Thanks.
I was i bit confused about how you could load more than one module in
the application. I've just found the subModule concept and everything
makes sense now.
Thanks again....
Massimo Lusetti wrote:
On 2/13/07, Hugo Palma <[EMAIL PROTECTED]> wrote:
I couldn't find in the docs how Tapestry finds the module builder(s) for
the running application. I can see that for packaged modules it gets the
info from META-INF, but what are the rules for the application provided
module builders ?
I started testing and i could see that AppModule class gets picked up
but App2Module doesn't. That's when i decided to ask here for the rules
as i'm sure if i started guessing i'd probably miss something.
It's the name of your filter configured within web.xml plus Module
suffix. So since the default name for Tapestry is app then it comes
AppModule.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
