You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2002/10/15 10:47:30 UTC
DO NOT REPLY [Bug 13643] New: -
[PATCH] Finer granularity for RequestFactory impl choice
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=13643>.
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=13643
[PATCH] Finer granularity for RequestFactory impl choice
Summary: [PATCH] Finer granularity for RequestFactory impl choice
Product: Cocoon 2
Version: Current CVS
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: core
AssignedTo: cocoon-dev@xml.apache.org
ReportedBy: leo.sutic@inspireinfrastructure.com
Currently, the RequestFactory must be chosen at a classloader level. That is,
no two pipelines or servlets that share the same classloader can have different
request factories. This means that in a servlet environment where cocoon is
being served up to all servlets as a common library, they must all have the
same request factory.
It also makes it impossible to select request factory on a per-pipeline basis,
as has been recently discussed.
This patch removes the static factory variable in RequestFactory, and instead
lets the request factory be passed to the HttpRequest via the environment.
It still isn't pipeline-scoped request factories, but there is now a
possibility of having such.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org