On Tue, 15 Oct 2013 18:34:09 -0300, Lance Java <lance.j...@googlemail.com>
wrote:
I don't recommend this at all, in fact I think it is a terrible idea....
but if you really want to stop tapestry from creating reloadable proxies,
you can declare your services by concrete class instead of by interface
in your AppModule.
In addition, any service declared based on an interface will be proxied,
so casting it to the implementation class won't work. As Lance said, if
you need to use service implementation methods that aren't in the service
interface, you're probably needing to add them to the service interface or
rethinking your architecture.
--
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
