[
https://issues.apache.org/jira/browse/TAP5-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1943:
---------------------------------
Labels: bulk-close-candidate (was: test)
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.
> Tapestry Spring unable to inject interface by name when testing
> ---------------------------------------------------------------
>
> Key: TAP5-1943
> URL: https://issues.apache.org/jira/browse/TAP5-1943
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-spring
> Affects Versions: 5.3.3
> Reporter: Matt Raible
> Labels: bulk-close-candidate
>
> This did work in previous versions of Tapestry, but no longer. Here's the
> mailing list thread:
> http://tapestry.1045711.n5.nabble.com/Tapestry-5-3-3-Spring-3-1-and-Inject-td5711099.html
> Here's a workaround:
> http://stackoverflow.com/questions/2684171/tapestry-5-and-spring-beans-with-same-interface
> This is only needed for testing, everything works fine at runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
