ith 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.
> >
> >
> >
>
> --
&g
t; 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
This is a big stumbling point in Tapestry that injection is different
from components (including pages, mixins, and base component classes)
and for services.
Injection for services is part of the Inversion of Control container,
and its a bit less "magic". Tapestry takes it as far as providing the
You can only use @Inject in classes that are under the control of tapestry.
that is classes under .base .components and .pages
If you want to use services in other classes you have to inject them yourself.
see http://tapestry.apache.org/tapestry5/tapestry-ioc/index.html
2008/2/22, Mahen Perera <
Hi all,
A quick one,
Can we inject services using @Inject in any class,, or is it restricted
to only Page classes. I mean classes which are in web.pages package.
Thanks in advance for all replies.
The information contained in this email is strictly confidential and for the
use of t
