[TAPESTRY-760] Application startup fails occasionally because of undefined order of contributions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0
• Fix Version/s: 4.0
• Component/s: Framework
• Environment: Windows NT; IBM JDK 1.4.1, Tapestry-4.0-beta-13
• Assignee: Howard Lewis Ship
• Reporter: Michael Frericks
• Created: 17/Nov/05 22:56
• Updated: 17/Dec/05 03:01
• Resolved: 17/Dec/05 02:37

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>

Issue Links

• is duplicated by: TAPESTRY-807 Tapestry 4.0 RC-1 Incompatible w/ Sun JDK 1.3.1 and IBM (WAS 5.0.1) JDK 1.31
• is related to: TAPESTRY-787 Port late bug fixes from 4.0 branch to trunk