You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/02/19 07:32:13 UTC
DO NOT REPLY [Bug 17190] New: -
Classloader-problem with xerces not seeing webapp-classes
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=17190>.
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=17190
Classloader-problem with xerces not seeing webapp-classes
Summary: Classloader-problem with xerces not seeing webapp-
classes
Product: Tomcat 4
Version: 4.1.18
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Major
Priority: Other
Component: Unknown
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: Suran@gmx.net
This is similar to bug 16221 but way more serious.
We have a web-application that uses Xerces2 and gives
it a class-name to instanciate for the document-class.
However since tomcat uses Xerces2 now (4.0.3 with xerces1
works fine) the endorsed xerces2 is used. But this xerces2
does not see the classes of the servlet's war-file or the
libraries therein that it was called from and thus does
not function correctly aynmore.
Due to bug 16221 we cannot use the xerces2 (that is _not_
part of j2se or the servlet-api) inside our war-file as
stated in the documentation.
It does work if our application-classes are copied to the endored-
directory and we could not make xerces2 not globaly visible by
having it in the server/lib -directory.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: Tomcat Standalone - 302 Redirect Issue
Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "neal" <ne...@yahoo.com>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Tuesday, February 18, 2003 10:36 PM
Subject: Tomcat Standalone - 302 Redirect Issue
>
>
> Can someone please confirm the option to switch the welcome file behavior
> from a redirection to a rd.forward was included in the mapper for Tomcat
> 5.0? I have heard both that it was and that it wasn't.
>
> I guess I have the following questions still:
>
> 1. Is this functionality going to be included in Tomcat 5?
As of last (long) weekend, it is included in Tomcat 5. But before people
get confused, it isn't a true rd.forward. It works more like an
Apache/httpd rewrite.
> 2. Where/when can I find documentation on how to configure this new
feature?
When is still an open question (patches are always welcome :). The
configuration option is 'processWelcomeResources' on the Connector element
('true' means forward, 'false' is the old TC 4.x behavior: The current
default is 'true').
> 3. When will a release candidate of Tomcat5 be available? I understand
> there are not set dates for these sorts of things but a general ballpark
> idea would help me to plan.
My limited understanding of this is that, as a JCP member, Apache can't have
a 'release' version before the Servlet-2.4 & JSP-2.0 Specs go final (but
IANAL). This means that anyone that actually knows the answer is under an
NDA, so they can't tell you.
>
> Thanks.
> Neal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Tomcat Standalone - 302 Redirect Issue
Posted by neal <ne...@yahoo.com>.
Can someone please confirm the option to switch the welcome file behavior
from a redirection to a rd.forward was included in the mapper for Tomcat
5.0? I have heard both that it was and that it wasn't.
I guess I have the following questions still:
1. Is this functionality going to be included in Tomcat 5?
2. Where/when can I find documentation on how to configure this new feature?
3. When will a release candidate of Tomcat5 be available? I understand
there are not set dates for these sorts of things but a general ballpark
idea would help me to plan.
Thanks.
Neal
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org