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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]