You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Martin Papy (Created) (JIRA)" <ji...@apache.org> on 2011/10/13 13:01:12 UTC
[jira] [Created] (TAP5-1693) Improper Detection of "String" Beans
in Symbol Injection
Improper Detection of "String" Beans in Symbol Injection
--------------------------------------------------------
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
Priority: Blocker
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
[jira] [Assigned] (TAP5-1693) Improper Detection of "String" Beans
in Symbol Injection
Posted by "Howard M. Lewis Ship (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1693:
------------------------------------------
Assignee: Howard M. Lewis Ship
> Improper Detection of "String" Beans in Symbol Injection
> --------------------------------------------------------
>
> 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: Blocker
> 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
[jira] [Commented] (TAP5-1693) Improper Detection of "String" Beans
in Symbol Injection
Posted by "Howard M. Lewis Ship (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129029#comment-13129029 ]
Howard M. Lewis Ship commented on TAP5-1693:
--------------------------------------------
Are you running in Tapestry 5.0 compatibility mode? You'll see a tapestry.use-external-spring-context init-parameter in web.xml when this is the case.
> Improper Detection of "String" Beans in Symbol Injection
> --------------------------------------------------------
>
> 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
> Priority: Blocker
> 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
[jira] [Closed] (TAP5-1693) Spring beans of type java.lang.String
can confuse Tapestry, which will use them in preference to other
injections, such as @Symbol
Posted by "Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1693.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3
> 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
[jira] [Updated] (TAP5-1693) Improper Detection of "String" Beans
in Symbol Injection
Posted by "Martin Papy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Papy updated TAP5-1693:
------------------------------
Attachment: screenshot-1.jpg
Eclipse Debug Mode
We can clearly see :
- the Spring "core-context.xml" file that defined the String Bean ( and in comment the JNDI lookup equivalent that is usually used )
- the TapestryModule class filewith the Debug pointbreak when trying to create a HttpServletRequestHandler
- the wrong injected value "applicationCharset" (should display UTF-8)
> Improper Detection of "String" Beans in Symbol Injection
> --------------------------------------------------------
>
> 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
> Priority: Blocker
> 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
[jira] [Commented] (TAP5-1693) Improper Detection of "String" Beans
in Symbol Injection
Posted by "Howard M. Lewis Ship (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129023#comment-13129023 ]
Howard M. Lewis Ship commented on TAP5-1693:
--------------------------------------------
public HttpServletRequestHandler buildHttpServletRequestHandler(Logger logger,
List<HttpServletRequestFilter> configuration,
@Primary
RequestHandler handler,
@Symbol(SymbolConstants.CHARSET)
String applicationCharset,
SessionFactory sessionFactory)
Interesting. Obviously, Tapestry should be doing an injection of the Symbol, but instead is picking up the Spring Bean whose type is String. This is probably just an ordering issue ... we need to check Spring a bit later in the MasterObjectProvider chain.
> Improper Detection of "String" Beans in Symbol Injection
> --------------------------------------------------------
>
> 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
> Priority: Blocker
> 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
[jira] [Commented] (TAP5-1693) Improper Detection of "String" Beans
in Symbol Injection
Posted by "Howard M. Lewis Ship (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129023#comment-13129023 ]
Howard M. Lewis Ship commented on TAP5-1693:
--------------------------------------------
public HttpServletRequestHandler buildHttpServletRequestHandler(Logger logger,
List<HttpServletRequestFilter> configuration,
@Primary
RequestHandler handler,
@Symbol(SymbolConstants.CHARSET)
String applicationCharset,
SessionFactory sessionFactory)
Interesting. Obviously, Tapestry should be doing an injection of the Symbol, but instead is picking up the Spring Bean whose type is String. This is probably just an ordering issue ... we need to check Spring a bit later in the MasterObjectProvider chain.
> Improper Detection of "String" Beans in Symbol Injection
> --------------------------------------------------------
>
> 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
> Priority: Blocker
> 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
[jira] [Commented] (TAP5-1693) Improper Detection of "String" Beans
in Symbol Injection
Posted by "Howard M. Lewis Ship (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129029#comment-13129029 ]
Howard M. Lewis Ship commented on TAP5-1693:
--------------------------------------------
Are you running in Tapestry 5.0 compatibility mode? You'll see a tapestry.use-external-spring-context init-parameter in web.xml when this is the case.
> Improper Detection of "String" Beans in Symbol Injection
> --------------------------------------------------------
>
> 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
> Priority: Blocker
> 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
[jira] [Updated] (TAP5-1693) Spring beans of type java.lang.String
can confuse Tapestry, which will use them in preference to other
injections, such as @Symbol
Posted by "Howard M. Lewis Ship (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1693:
---------------------------------------
Priority: Critical (was: Blocker)
Summary: Spring beans of type java.lang.String can confuse Tapestry, which will use them in preference to other injections, such as @Symbol (was: Improper Detection of "String" Beans in Symbol Injection)
> 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
[jira] [Updated] (TAP5-1693) Spring beans of type java.lang.String
can confuse Tapestry, which will use them in preference to other
injections, such as @Symbol
Posted by "Howard M. Lewis Ship (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1693:
---------------------------------------
Priority: Critical (was: Blocker)
Summary: Spring beans of type java.lang.String can confuse Tapestry, which will use them in preference to other injections, such as @Symbol (was: Improper Detection of "String" Beans in Symbol Injection)
> 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
[jira] [Assigned] (TAP5-1693) Improper Detection of "String" Beans
in Symbol Injection
Posted by "Howard M. Lewis Ship (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1693:
------------------------------------------
Assignee: Howard M. Lewis Ship
> Improper Detection of "String" Beans in Symbol Injection
> --------------------------------------------------------
>
> 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: Blocker
> 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
[jira] [Commented] (TAP5-1693) Spring beans of type
java.lang.String can confuse Tapestry, which will use them in preference to
other injections, such as @Symbol
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (TAP5-1693) Improper Detection of "String" Beans
in Symbol Injection
Posted by "Martin Papy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Papy updated TAP5-1693:
------------------------------
Attachment: screenshot-1.jpg
Eclipse Debug Mode
We can clearly see :
- the Spring "core-context.xml" file that defined the String Bean ( and in comment the JNDI lookup equivalent that is usually used )
- the TapestryModule class filewith the Debug pointbreak when trying to create a HttpServletRequestHandler
- the wrong injected value "applicationCharset" (should display UTF-8)
> Improper Detection of "String" Beans in Symbol Injection
> --------------------------------------------------------
>
> 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
> Priority: Blocker
> 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
[jira] [Closed] (TAP5-1693) Spring beans of type java.lang.String
can confuse Tapestry, which will use them in preference to other
injections, such as @Symbol
Posted by "Howard M. Lewis Ship (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1693.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3
> 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
[jira] [Commented] (TAP5-1693) Spring beans of type
java.lang.String can confuse Tapestry, which will use them in preference to
other injections, such as @Symbol
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ 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