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-16 14:39 ------- Thanks again for your input Berin, perhaps I haven't correctly conveyed the problem I'm trying to solve here. The issue is with *custom* ThreadSafe components, defined in the user.roles file, that implement Contextualizable, and wish to do as you say, namely, access context values directly inside contextualize(). Saving a reference to the context object and retrieving the variables on-demand as you also describe would work, but I'd like to find a solution for both types of usage (ie. saving a reference to the context, and accessing the context values in contextualize()) Due to the currently implemented calling order, contextualize() will be called on custom ThreadSafe components defined in user.roles during Cocoon's startup, before a CocoonServlet subclass has a chance to add any custom values to the Cocoon context. This means the component will fail to read any custom context values it needs in contextualize(), because they won't yet exist. This is what I was trying to solve. There doesn't seem to be any opportunity before CocoonServlet.createCocoon() to add them, and after it is too late. I hope that makes it a bit clearer, all Cocoon components are ok and all other types of custom components are ok, only custom ThreadSafe components are affected by this problem. Sorry if I've repeated what you're already understood. If I have, then I must have completely missed your previous point about keeping references to the same context object ?? If I have, please tell me :) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
