hi peter, ASOs that have a (non-empty) constructor can be instantiated by contributing to the ApplicationStateManager service. Please see the thread for the source. if you contribute to this service you can still use the @ApplicationState annotation.
http://www.nabble.com/-T5-Question-on-ASO-configuration-tf3399851.html#a9469215 g, kris Chris Lewis <[EMAIL PROTECTED]> 15.10.2007 08:09 Bitte antworten an "Tapestry users" <users@tapestry.apache.org> An Tapestry users <users@tapestry.apache.org> Kopie Thema Re: Tapestry 5 service configuration Hi Peter 1) I think the general opinion on this is that a service and an aso are completely different animals. I can't think of a situation where I'd ever want an aso to be a service (or vice versa), but that's just me. If there is a way to do this, someone else will need to chime in. 2) @Inject it. Assuming you bound or built your service, you can simply inject it using @Inject as the general type (usually an interface) of object, and Tapestry IoC will resolve it for you. sincerely, chris Peter Stavrinides wrote: > Hi all, > > Following on from a previous post on this subject I have some > questions on Tapestry 5 IoC: > > 1. How do you register an ASO as a service if you have to provide > arguments to the constructor (i.e. you cannot use @ApplicationState in > this case). > > 2. How do you retrieve a service object that has been contributed to > the framework > > Thanks > Peter > > --------------------------------------------------------------------- > 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]
