Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-760

Application startup fails occasionally because of undefined order of contributions

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.0
    • Fix Version/s: 4.0
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      Windows NT; IBM JDK 1.4.1, Tapestry-4.0-beta-13

      Description

      The order of contributions to 'tapestry.init.ApplicationInitializers' is important. Otherwise a NPE occurs.

      The "service:tapestry.init.ApplicationSpecificationInitializer" has to be executed before "service:tapestry.globals.SetupServletApplicationGlobals".

      The ApplicationSpecificationInitializer sets values the SetupServletApplicationGlobals relies on.

      Solution:

      Change in 'tapestry.init.xml':

      <contribution configuration-id="ApplicationInitializers">
      <command id="WebContextInitializer" object="service:WebContextInitializer" before="*"/>
      <command id="ApplicationSpecificationInitializer" object="service:ApplicationSpecificationInitializer"/>
      </contribution>

      to

      <contribution configuration-id="ApplicationInitializers">
      <command id="WebContextInitializer" object="service:WebContextInitializer" before="*"/>
      <command id="ApplicationSpecificationInitializer" object="service:ApplicationSpecificationInitializer" before="tapestry.globals.SetupServletApplicationGlobals" />
      </contribution>

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                hlship Howard M. Lewis Ship
                Reporter:
                frericksm Michael Frericks
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: