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=36494>. 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=36494 ------- Additional Comments From [EMAIL PROTECTED] 2005-11-04 10:46 ------- Based on what Greg Wilkins (via Felix) says in #37224 and Josias' comment below: * The org.apache.cocoon.environment.Request implementation of o.a.l.cms.ac.DocumentPolicyManagerWrapper.request actually wraps a javax.servlet.http.HttpServletRequest * The lifetime of a DocumentPolicyManagerWrapper is actually beyond the scope of an HttpServletRequest * Which results in a reference of the HttpServletRequest living outside it's natural scope of HttpServlet.service/other HTTP method, which is wrong. If the above is true and the scope of a DocumentPolicyManagerWrapper is beyond the scope of an HTTP request, then it should not have such a request as a (members' ) member. After a bit more digging and my very poor understanding of the architecture here, this request member of the DocumentPolicyManagerWrapper is there to optimize (a o.a.l.cms.repository)sessions by calling RepositoryUtil right? But a datastore session sounds like something that should be lightweight (and is supposed to cover a single unit of work) so i dont see the need for that... If i'm wrong or alternatively, this needs another pattern to optimize things like a threadlocal or something to store a session per HTTP request. Sorry for bubbling or if all this is not accurate, i just *really* need someone more experienced with the codebase to solve this one, it's a major showstopper for me right now; i'm really stuck :-( -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
