You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Michael Frericks (JIRA)" <ta...@jakarta.apache.org> on 2005/11/17 14:56:41 UTC
[jira] Created: (TAPESTRY-760) Application startup fails occasionally because of undefined order of contributions
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Commented: (TAPESTRY-760) Application startup fails occasionally because of undefined order of contributions
Posted by "Alex Victoria (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-760?page=comments#action_12360607 ]
Alex Victoria commented on TAPESTRY-760:
----------------------------------------
I guess I didn't find this duplicate issue because I had limited my search to JDK 1.3 issues. Thanks.
> 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
> Assignee: Howard M. Lewis Ship
> Fix For: 4.0
>
> 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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Assigned: (TAPESTRY-760) Application startup fails occasionally because of undefined order of contributions
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-760?page=all ]
Howard M. Lewis Ship reassigned TAPESTRY-760:
---------------------------------------------
Assign To: Howard M. Lewis Ship
> 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
> Assignee: Howard M. Lewis Ship
>
> 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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[jira] Closed: (TAPESTRY-760) Application startup fails occasionally because of undefined order of contributions
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-760?page=all ]
Howard M. Lewis Ship closed TAPESTRY-760:
-----------------------------------------
Fix Version: 4.0
Resolution: Fixed
> 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
> Assignee: Howard M. Lewis Ship
> Fix For: 4.0
>
> 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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org