Hi Howard, Since service does not subject to run time manipulation of Tapestry, does that mean we can debug a service easier than a page class? for the page class, it's strict that they have to be placed inside the pages package, same with components, but we can place a service class anywhere, is that the reason? any special handing from Tapestry for classes inside the services package? thanks.
A.C. Howard Lewis Ship wrote: > > > The long and short of it is: services are (effectively) simple > singletons with a easy and constant lifecycle and no mutable internal > state. Pages and components are mired in the much more complex page > lifecycle and the component hierarchy of the page and have > considerable mutable internal state. > > > -- View this message in context: http://www.nabble.com/injecting-services-in-T5-tp15637694p15641994.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
