You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2016/02/22 14:45:20 UTC

[jira] [Updated] (TAP5-1955) Documentation on ServiceBinder#bind(Class implementationClass) is wrong/lacks extra information

     [ https://issues.apache.org/jira/browse/TAP5-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-1955:
---------------------------------
    Labels: bulk-close-candidate  (was: )

This issue affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent version of Tapestry (currently 5.4.0, available from Maven Central), please update it as soon as possible and add '5.4.0') to the issue's affected versions.

> 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
>              Labels: bulk-close-candidate
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)