[jira] [Updated] (TAP5-1196) Decorator methods for non existent services should fail with a message

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-1196:
---------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, 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 development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> 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.2#6252)