On Sat, 05 Apr 2014 15:46:26 -0300, Sanket Sharma <sanketsha...@gmail.com>
wrote:
Sorry, I wrote that email in a rush - should have been more explicit.
Let me try and explain with code:
public class MyServiceImpl implements MyService {
@Inject //This is not supported for
services,
will not work
ServiceB serviceB;
The field should be private. If yes, it should work, even if most people
(me very included) recommend that injection in services should be done by
constructor. I don't even add @Inject to constructor parameters, so my
services classes are completely independent of Tapestry-IoC unless some
other annotation like @Symbol is needed.
Thank you for the clarification regarding proxies/services.
My pleasure. :)
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
