You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/06/03 21:38:45 UTC
[jira] Updated: (TAPESTRY-2369) Initialization of linkZone and zone
is order dependent & can fail
[ https://issues.apache.org/jira/browse/TAPESTRY-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2369:
-------------------------------------------
Fix Version/s: (was: 5.0.12)
5.0.13
> Initialization of linkZone and zone is order dependent & can fail
> -----------------------------------------------------------------
>
> Key: TAPESTRY-2369
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2369
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Environment: Java 1.5, Jboss 4.2, Windows XP
> Reporter: Ben Sommerville
> Priority: Minor
> Fix For: 5.0.13
>
> Attachments: TAPESTRY-2369.patch
>
>
> The Tapestry.init function is used to initialize zones and links to zones. The linkZone init function has a dependency on the zone init function (because it assumes that the zone element/object has been created).
> The code that creates the init call has no mechanism for specifying the order in which init functions are called. The final order will depend on the ordering of the init function hash map. i.e. indeterminate.
> When running the tapestry tests via maven and Jetty the zone init works. Running the same code under JBoss the order of the zone & linkZone init calls is reversed, leading to the linkZones not working.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org