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 Fri, 12 Apr 2002 15:53:25 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 crafterm@fztig938.bank.dresdner.net  2002-04-12 15:53 -------
I brought up subclassing cocoon on 
http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=99133438620457&w=2
and it received a positive response. Also, if it's not meant to be subclassed,
it should be marked final.

The change is an attempt to fix a problem described at:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=101681223003344&w=2
I described several options to fix the issue, this one was the easiest as
Cocoon.appContext also has protected access - do you think one of the others
proposals would be more appropriate ? As it currently stands, it is not possible
to add context values for threadsafe user-role components.

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


Mime
View raw message