I just to say maybe the concept problem is you are dealing with is the concept of persistence with Pojo's using Inversion of Control , so you are mixed-up. many folk have talk about the good of ioc .Now could you give me a explain of how t5 manage the service and aso?
Peter Stavrinides wrote: > > As far as I'm concerned service is an ugly word everyone likes to throw > around, what you are really dealing with is the concept of persistence > with Pojo's using Inversion of Control. > > Peter Stavrinides wrote: >> A concept problem? really?? now I am curious as to what this concept >> problem actually, is could you explain it. >> >> Peter >> >> MavenMan wrote: >>> >>> Peter Stavrinides wrote: >>>> Hi Chris >>>> ApplicationStateManager is a service , I also think a service and an >>>> aso are completely different thing. >>>> >>>> in a word, It is a concept problem. >>>> >>>>> are completely different >>>> >>>> I am no expert on T5, but strongly disagree with you. >>>> >>>> Peter >>>> >>>> Chris Lewis wrote: >>>>> 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] >>>>> >>>> --------------------------------------------------------------------- >>>> 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] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Tapestry-5-service-configuration-tf4624618.html#a13210596 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
