If I'm not clear enough, please say. In a simpler way. I include extra modules in my application using * -Dtapestry.modules* JVM parameter. Within one of those modules, the main module class is under the package *my.package* so my module's class fully qualified name is *my.package.mymodule*.
Now I need to have a comparator, so I figured to add it to the *base*package, which would be *my.package.base* but when I try to instantiate an instance of that comparator, tapestry complains that that I cannot be instantiate that class (i.e. my comparator) because it has been transformed. Although it's under a base package. Should I specify my side module's main package somewhere ? Thanks *---------------------* *Muhammad Gelbana* http://www.linkedin.com/in/mgelbana On Thu, Oct 3, 2013 at 11:19 PM, Muhammad Gelbana <m.gelb...@gmail.com>wrote: > I'm running my web project with jetty while including my module classed > using the jvm parameter > > -Dtapestry.modules=my.package.module1,my.package.module2, > my.package.module3 > > In one of those modules, I have a class in the base package, typically: > > *com.skycomm.ipkaizen.portal.admin.base.ProbeCommandResponseSorter* > > The module's qualified name is > > *com.skycomm.ipkaizen.portal.admin.services.PortalAdminModule* > > Isn't it enough to mention the module's qualified name in the * > tapestry.modules* jvm parameter for the * > com.skycomm.ipkaizen.portal.admin.base* package to be identified and > excluded from runtime modifications ?? > > > Regards > *---------------------* > *Muhammad Gelbana* > http://www.linkedin.com/in/mgelbana >
