Per request, I actually don't have a xercesImpl.jar file that is being used (there is one but it's not being ran). However, I do have a file named a_xercesImpl.jar that is being used by the webapp (located in webapps\<webapp>\WEB-INF\lib. I did verify that the a_xercesImpl.jar file contains the class DocumentBuilderFactoryImpl.
Now for some history that might help explain some of this. The product is written in Java 1.4 and shipped with an older version of Tomcat (5.0 I think - it uses procrun 1.0 if that's any help). Since the product is supposed to support running under any J2EE compliant application server, we opted to go with the more stable release of Apache Tomcat 5.5.23 and JVM 1.5. And all we did to get the product to run in Apache Tomcat 5.5.23 is moved the webapp folder from the initial installation folder of Tomcat 5.0 to the webapp folder of Tomcat 5.5. That included any of the JAR files in that hiearchy. Thanks, Tony -----Original Message----- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Friday, October 27, 2000 11:19 AM To: Tony Fountain Subject: Re: Class loading issue Please post to group where (in tomcat) is your xercesImpl.jar located? Thx/ M-- ----- Original Message ----- From: "Tony Fountain" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Friday, October 26, 2007 11:11 AM Subject: RE: Class loading issue The exact error is this: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Caused by: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source) at org.apache.commons.modeler.util.DomUtil.readXml(DomUtil.java:241) at org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource.execute(Mb eansDescriptorsDOMSource.java:87) at org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource.loadDescri ptors(MbeansDescriptorsDOMSource.java:77) at org.apache.commons.modeler.Registry.load(Registry.java:791) at org.apache.commons.modeler.Registry.loadDescriptors(Registry.java:900) at org.apache.commons.modeler.Registry.loadMetadata(Registry.java:267) at org.apache.catalina.storeconfig.StoreConfigLifecycleListener.createMBean (StoreConfigLifecycleListener.java:93) at org.apache.catalina.storeconfig.StoreConfigLifecycleListener.lifecycleEv ent(StoreConfigLifecycleListener.java:58) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu pport.java:120) at org.apache.catalina.core.StandardServer.start(StandardServer.java:705) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) .. 6 more That's the entire contents of the stdout log file. I don't mind moving the vendor specific jar files to the \common\lib folder, but I would like to make sense of why it happens as well. Note that implementing this product is my first exposure in 15 years of programming to Java / Apache technologies :). Not that they (.NET / IIS vs Java / Apache) are too dissimilar, rather it's the implementation topics like this I struggle with at the moment. Thanks, Tony -----Original Message----- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Friday, October 26, 2007 9:51 AM To: Tomcat Users List Subject: RE: Class loading issue > From: Tony Fountain [mailto:[EMAIL PROTECTED] > Subject: Class loading issue > > but when the webapp loads, one of the classes it requires generates an > error the first time the webapp is accessed via the browser. What error? Do you have an associated stack trace? Is there anything in the logs? Note that common/lib is visible not only to the webapp, but also to the container classes. Just speculating, but if the classes in question are used somehow for something like container-managed connection pooling, they must be visible to Tomcat as well as the webapp. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ________________________________________________________________________ This Email has been scanned for all viruses by PAETEC Email Scanning Services, utilizing MessageLabs proprietary SkyScan infrastructure. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.paetec.com. ________________________________________________________________________ --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ________________________________________________________________________ This Email has been scanned for all viruses by PAETEC Email Scanning Services, utilizing MessageLabs proprietary SkyScan infrastructure. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.paetec.com. ________________________________________________________________________ --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
