You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/08/18 19:07:16 UTC

[jira] Updated: (TAP5-1232) Restore injection of service id (as a String) into service decorator methods for proper backwards compatibility

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

Howard M. Lewis Ship updated TAP5-1232:
---------------------------------------

    Summary: Restore injection of service id (as a String) into service decorator methods for proper backwards compatibility  (was: Removed auto-injection of service ids as String is backward incompatible with decorators)

> Restore injection of service id (as a String) into service decorator methods for proper backwards compatibility
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1232
>                 URL: https://issues.apache.org/jira/browse/TAP5-1232
>             Project: Tapestry 5
>          Issue Type: Bug
>    Affects Versions: 5.2.0
>            Reporter: Igor Drobiazko
>            Assignee: Igor Drobiazko
>             Fix For: 5.2.1
>
>
> In this discussion we decided to turn off the injection of service ids as Strings.
> http://markmail.org/thread/bgue2rsmaxjt3xhs
> Unfortunately we forgot about the decorators. Tapestry's documentation contains examples in which a service id in injected when building a decorator.
> http://tapestry.apache.org/tapestry5.1/tapestry-ioc/decorator.html
> Even though dacorator API is deprecated, there are still apps using this feature. They will be broken after upgarde to 5.2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.