On Fri, 08 Jun 2012 17:16:22 -0300, Carsten Klein (JIRA) <j...@apache.org>
wrote:
Defines a service in terms of an implementation class, without a
service interface. In this case, the service
will not be proxiable (proxying requires a service interface) and
{@link ServiceDef#getServiceInterface()} will
return the implementation class. In this situation, the service will
not be proxied; it will be instantiated
fully on first reference (ignoring its scope, if any) and will not be
decorated.
In tapestry-core InternalModule I found usages of that interface, where
you bind an interface class.
Looking at the code, the implementation will try to resolve the
implementation class and then bind
it using the standard bind(Class<T> serviceInterface, Class<? extends T>
implementationClass) method.
That part of the documentation talks about binding a service using only a
concrete class and you're talking about binding a service using an
interface, so the documentation is correct, maybe just not clear enough.
Again, please post in the Tapestry user mailing list before posting a JIRA.
Cheers!
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
