tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Klein (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TAP5-1955) Documentation on ServiceBinder#bind(Class<T> implementationClass) is wrong/lacks extra information
Date Fri, 08 Jun 2012 20:16:22 GMT
Carsten Klein created TAP5-1955:
-----------------------------------

             Summary: Documentation on ServiceBinder#bind(Class<T> implementationClass)
is wrong/lacks extra information
                 Key: TAP5-1955
                 URL: https://issues.apache.org/jira/browse/TAP5-1955
             Project: Tapestry 5
          Issue Type: Improvement
          Components: tapestry-core
    Affects Versions: 5.3.3
            Reporter: Carsten Klein
            Priority: Minor


The documentation on the above mentioned method states that

> 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.

Bound as such, the interface can both be proxied and decorated.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message