Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1693

Spring beans of type java.lang.String can confuse Tapestry, which will use them in preference to other injections, such as @Symbol

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 5.3
    • 5.3
    • None

    Description

      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.

      Attachments

        Activity

          People

            hlship Howard Lewis Ship
            kheldar666 Martin Papy
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: