Application startup fails occasionally because of undefined order of
contributions
----------------------------------------------------------------------------------
Key: TAPESTRY-760
URL: http://issues.apache.org/jira/browse/TAPESTRY-760
Project: Tapestry
Type: Bug
Components: Framework
Versions: 4.0
Environment: Windows NT; IBM JDK 1.4.1, Tapestry-4.0-beta-13
Reporter: Michael Frericks
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>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
