[
https://issues.apache.org/jira/browse/TAP5-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulrich Stärk updated TAP5-809:
------------------------------
Labels: bulk-close-candidate (was: )
This issue has been last updated more than 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, please update it as soon as possible. In the case of a feature
request, please discuss it with the Tapestry developer community on the
d...@tapestry.apache.org mailing list first.
> Spring services should be decoratable
> -------------------------------------
>
> Key: TAP5-809
> URL: https://issues.apache.org/jira/browse/TAP5-809
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-spring
> Affects Versions: 5.1.0.5
> Reporter: Carl Crowder
> Labels: bulk-close-candidate
> Attachments: spring_service_decoration.patch
>
>
> SpringBeanServiceDef returns "true" for isPreventDecoration() which causes
> any attempts to decorate services created in Spring to fail silently.
> As far as I can tell there's no need for them to not be decoratable - I asked
> on the mailing list and noone objected, and having changed it locally the
> tests all run fine.
> If there is a valid reason then at least the service builder should log a
> warning rather than plunge on ignoring the decoration method.
> I've attached a (very simple) patch to enable decoration of spring services.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
