A solution would be to let listeners instantiate all ModuleDef, let them store these definition objects in application context, and let TapestryFilter (as the main filter of our application) aggregate all the extra module definitions before initializing Tapestry Registry.
BTW i will try to implement this to see if it provides flexibility or is blocking in other ways... Best Regards, Christophe Cordenier. 2010/2/9 cordenier christophe <[email protected]> > Thanks for your quick answer, > > I wanted also to talk about Registry reloading and runtime deployement. As > Tapestry Tynamo does it with RestEasy API, we should have a way to > contribute externally to the Tapestry Registry and reload it. That means > instead of initializing other Framework in Tapestry contributions, people > who uses other technologies would be able to have access to the Tapestry > Registry to add their implementation of Tapestry Services directly > accessible from Tapestry pages. > > It sounds like an inversion of control but at the contribution level, maybe > it's a non-sense ... I am wondering. > > Best Regards, > Christophe. > > 2010/2/9 Howard Lewis Ship <[email protected]> > > I think the goal there was to minimize the number of things that need >> to be configured inside web.xml. However, you are right ... there >> should be some easy to use API somewhere to let you initialize the >> Spring support, as SpringTapestryFilter does, even when not using >> SpringTapestryFilter. >> >> On Tue, Feb 9, 2010 at 5:49 AM, Cordenier Christophe >> <[email protected]> wrote: >> > Hi, >> > >> > Currently the Tapestry Registry is initialized by TapestryFilter. I was >> looking at the Tynamo Resteasy implementation that initializes resteasy >> application context with an extension of TapestryFilter. >> > On the other side TapestrySpringFilter also extends default >> TapestryFilter. >> > >> > I have seen that other framework like Resteasy or Spring... provide a >> servlet context listener as their bootstrap, so it becomes easier to order >> application bootstraping. And resolve the multiple inheritance problem. >> > >> > Sound it reasonable to implement an alternative way to launch Tapestry >> registry via a Listener ? I Just wanted to have your point of view on this. >> > >> > Regards, >> > Christophe Cordenier. >> > >> > Developer of wooki @wookicentral.com >> > >> > ________________________________ >> > >> > Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? >> l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le >> secret professionnel. Si vous recevez ce message par erreur, merci d'en >> avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message >> ne pouvant ?tre assur?e sur Internet, la responsabilit? du groupe Atos >> Origin ne pourra ?tre recherch?e quant au contenu de ce message. Bien que >> les meilleurs efforts soient faits pour maintenir cette transmission exempte >> de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa >> responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un >> virus transmis. >> > >> > This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this >> e-mail in error, please notify the sender immediately and destroy it. As its >> integrity cannot be secured on the Internet, the Atos Origin group liability >> cannot be triggered for the message content. Although the sender endeavours >> to maintain a computer virus-free network, the sender does not warrant that >> this transmission is virus-free and will not be liable for any damages >> resulting from any virus transmitted. >> > >> >> >> >> -- >> Howard M. Lewis Ship >> >> Creator of Apache Tapestry >> >> The source for Tapestry training, mentoring and support. Contact me to >> learn how I can get you up and productive in Tapestry fast! >> >> (971) 678-5210 >> http://howardlewisship.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Regards, > Christophe Cordenier. > > Developer of wooki @wookicentral.com > -- Regards, Christophe Cordenier. Developer of wooki @wookicentral.com
