You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org> on 2014/06/27 17:35:31 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14046067#comment-14046067 ] 

Thiago H. de Paula Figueiredo commented on TAP5-1943:
-----------------------------------------------------

Matt, could you please post at small project with a test case for this issue? I couldn't find a way to reproduce it without spending too much time on it.

> 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
>            Priority: Critical
>              Labels: test
>
> 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.2#6252)