[
https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129144#comment-13129144
]
Hudson commented on TAP5-1693:
------------------------------
Integrated in tapestry-trunk-freestyle #578 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/578/])
TAP5-1693: Spring beans of type java.lang.String can confuse Tapestry,
which will use them in preference to other injections, such as @Symbol
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1185310
Files :
*
/tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/services/TapestryIOCModule.java
*
/tapestry/tapestry5/trunk/tapestry-spring/src/main/java/org/apache/tapestry5/internal/spring/SpringModuleDef.java
*
/tapestry/tapestry5/trunk/tapestry-spring/src/main/java/org/apache/tapestry5/spring/SpringConstants.java
*
/tapestry/tapestry5/trunk/tapestry-spring/src/main/java/org/apache/tapestry5/spring/SpringModule.java
*
/tapestry/tapestry5/trunk/tapestry-spring/src/test/webapp/WEB-INF/applicationContext.xml
> Spring beans of type java.lang.String can confuse Tapestry, which will use
> them in preference to other injections, such as @Symbol
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1693
> URL: https://issues.apache.org/jira/browse/TAP5-1693
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc, tapestry-spring
> Affects Versions: 5.3
> Reporter: Martin Papy
> Assignee: Howard M. Lewis Ship
> Priority: Critical
> Fix For: 5.3
>
> Attachments: screenshot-1.jpg
>
>
> I found a pretty confusing issue that seems Blocker to me.
> In my project I am using a JNDI name to configure a piece of my application.
> Basically in this case Spring creates of Bean of type "java.lang.String".
> That was perfectly working under Tapestry 5.2.6.
> Since I updated to 5.3-beta-19 1 time out of 3 the whole application if
> failling because Tapestry cannot resolve Page Name anymore.
> After digging it turns out that Tapestry is Injecting the value of this Bean
> in several places where it should not : example applicationCharset or
> startPageName.
> Please see attached screenshots for better understanding.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
