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

Jochen Kemnade closed TAP5-1196.
--------------------------------
    Resolution: Invalid

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the 
latest 5.4 preview release), feel free to provide the necessary information and 
reopen.

> Decorator methods for non existent services should fail with a message
> ----------------------------------------------------------------------
>
>                 Key: TAP5-1196
>                 URL: https://issues.apache.org/jira/browse/TAP5-1196
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.2
>            Reporter: Jim O'Callaghan
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> jc1 - Shouldn't decorator methods fail with a message that 'decorated xyz  
> service doesn't exist'?  It would make it a lot easier to find errors due to 
> service name changes etc.
> HLS contrib - Probably, if there is no @Match annotation, then the implicit 
> service id (from the method name) should be required to exist.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to