On Mon, 20 Aug 2012 11:16:28 -0300, George Christman
<gchrist...@cardaddy.com> wrote:
He say's what I'm calling a factory is actually a service locator and
that AutoMateParser should be defined as a service in the AppModule.
Yep . . .
He also stated the objects I use to pass in through the constructor now
need to be passed in through set methods
This isn't correct for Tapestry and not even for Spring. Both support
injection through constructors.
The last question where I'm still a little confused is related to using
services inside extended classes. Because I'm declaring
AutoMateParser.class as a service, but extending say Parser.class, would
I be able to inject my services inside my extended class without having
to declare Parser.class in my AppModule a service?
Yes.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org