I'm not sure if the bug is actually in the Jaxp version.. I will try to reproduce it, to see what happens moving around crimson jars..
For me seems it's in "Damn ClassLoaders" bug type.. :) Saludos , Ignacio J. Ortega > -----Mensaje original----- > De: Bill Barker [mailto:[EMAIL PROTECTED]] > Enviado el: viernes 5 de octubre de 2001 0:26 > Para: [EMAIL PROTECTED] > Asunto: Re: DO NOT REPLY [Bug 3961] - FactoryConfigurationError on > Servlet+JSP+taglib > > > I know that Costin has strong feeling on which Jaxp version > we should ship > with (I just don't remember what they are:). Does anyone else have an > opinion? > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, October 04, 2001 12:51 PM > Subject: DO NOT REPLY [Bug 3961] - FactoryConfigurationError on > Servlet+JSP+taglib > > > > 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=3961>. > > 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=3961 > > > > FactoryConfigurationError on Servlet+JSP+taglib > > > > > > > > > > > > ------- Additional Comments From > [EMAIL PROTECTED] 2001-10-04 > 12:51 ------- > > There seems to be a problem with the Jaxp jar files that > ship with RC1. > If you > > download Jaxp 1.1 from java.sun.com and replace the jar files in > lib/container > > with those, your example starts working. > > > > > > > *----* > > This message is intended only for the use of the person(s) > listed above > as the intended recipient(s), and may contain information that is > PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, > you may not read, copy, or distribute this message or any > attachment. > If you received this communication in error, please notify us > immediately > by e-mail and then delete all copies of this message and any > attachments. > > > In addition you should be aware that ordinary (unencrypted) > e-mail sent > through the Internet is not secure. Do not send confidential > or sensitive > information, such as social security numbers, account > numbers, personal > identification numbers and passwords, to us via ordinary > (unencrypted) > e-mail. >
