cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 7868] - [PATCH] protected createCocoon() in CocoonServlet
Date Mon, 15 Apr 2002 13:20:40 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7868>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7868

[PATCH] protected createCocoon() in CocoonServlet





------- Additional Comments From bloritsch@apache.org  2002-04-15 13:20 -------
No I am demonstrating that as long as your components store a reference to the
Context object, you will always have an up to date copy of the COntext information
available.

What point is there to a Context object if you don't get values from it?

It's a choice that you have to make.  If your COmponent will be satisfied
with never-changing values, then grab the info at Contextualize.

One thing that the ECM does not support is the Re** methods.  Recontextualize,
Reconfigure, Reparameterize, Recompose.

That is where you would handle things like that.  The Fortress abstract
container logic will eventually enable that in your systems.  That way you
can ensure that the Component will be available with the most up to date
Context object.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message