Yup, got that. Thank you all :)
*-*
*Muhammad Gelbana*
http://www.linkedin.com/in/mgelbana
On Fri, Oct 4, 2013 at 2:27 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> Muhammed, the base package is meant to be the place where you put
> superclasses of pages, c
Muhammed, the base package is meant to be the place where you put
superclasses of pages, components and mixins, so classes there will be
transformed. It's one of the Tapestry controlled packages. If you want
something not to be transformed, you have to put it somewhere.
On Thu, 03 Oct 2013
Thank you. Obviously I had a wrong idea about the *base* class.
*-*
*Muhammad Gelbana*
http://www.linkedin.com/in/mgelbana
On Fri, Oct 4, 2013 at 10:50 AM, Lance Java wrote:
> base, components, pages and mixins are special packages and anything in
> these packages is transfo
base, components, pages and mixins are special packages and anything in
these packages is transformed and loaded by a different classloader. These
packages are not suitable for utilities etc.
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'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.ProbeCommand
