Re: T5: Module builder discovery
?? Wed, 14 Feb 2007 05:00:44 +0800??Hugo Palma [EMAIL PROTECTED] ?? ??: 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. @Id(module_id) 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5: Module builder discovery
Documented here: http://tapestry.apache.org/tapestry5/tapestry-core/guide/conf.html 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. -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
T5: Module builder discovery
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.
Re: T5: Module builder discovery
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. -- Massimo http://meridio.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: T5: Module builder discovery
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]
