Jean-Baptiste Quenot-3 wrote:
>
> I commented on the issue, and finally marked it as invalid. Here
> is the comment, in case you wish to discuss it on the mailing-list
> or just for the record if other users came across this:
>
> It's a bit tricky to make the reloading work with Spring. You have
> to define class naming conventions and enforce them. The main idea
> behind all of this, is that you will come across problems if the
> same class is loaded in two different classloaders, one is the
> parent classloader, and the other is the reloading classloader.
>
> And of course please read the Javadoc thoroughly especially if you
> use Spring.
> --
> Jean-Baptiste Quenot
>
I noticed that the fellow how commented in the JIRA issue used the following
patterns:
ReloadingClassLoader.includePattern("info.jtrac.wicket.*");
ReloadingClassLoader.includePattern("info.jtrac.wicket.yui.*");
Is it necessary to explicitly specify the inclusion of sub-packages when the
parent package is already included? I only aske because our package
hierarchy is pretty deep when it comes to pages, and I'd loke to avoid
having to explicitly call each one of them out of just naming the root of
that part of the packager hierarchy is enough.
Thanks,
Matt
--
View this message in context:
http://www.nabble.com/Has-something-changed-in-markup-inheritance--tf3963374.html#a11331892
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
