[jira] [Commented] (TAP5-1693) Improper Detection of "String" Beans in Symbol Injection

["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