You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by bu...@apache.org on 2004/06/28 22:09:05 UTC
DO NOT REPLY [Bug 29850] New: -
Page should attach before finishLoad()
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29850>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29850
Page should attach before finishLoad()
Summary: Page should attach before finishLoad()
Product: Tapestry
Version: 3.0
Platform: All
OS/Version: Other
Status: NEW
Severity: Major
Priority: Other
Component: Framework
AssignedTo: tapestry-dev@jakarta.apache.org
ReportedBy: hlship@apache.org
Ok, I finally give. YES, the page should be attached to the request cycle and
to the engine BEFORE finishLoad() is invoke on it, or on any of its components.
In my case, I'm trying to make use of HiveMind; I need access to the HiveMind
Registry to initialize some of my component properties (which will be aliases
of services obtained from HiveMind's Registry). To get the Registry I need
the request cycle (to get the HttpServletRequest, to get the Registry from the
servlet context --- this is using the HiveMindFilter).
Still some room to hang yourself by initializing properties to client-specific
values.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org