You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2016/08/22 06:48:23 UTC
[jira] [Closed] (TAP5-1943) Tapestry Spring unable to inject
interface by name when testing
[ https://issues.apache.org/jira/browse/TAP5-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade closed TAP5-1943.
--------------------------------
Resolution: Incomplete
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.4.1 or newer), feel free to provide the necessary information and reopen.
> 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)