I checked in the tomcat and I have the latest xerces version and no crimson or parser.jar. I also checked under JBoss and found that the run.bat implicitly sets the parser factory to be a crimson factory rather than xerces. I changed that to xerces and replaced crimson.jar with xerces.jar and JBoss fails. There are several differences in tags that apparently xerces handles differently than crimson. I have the latest version of xerces anywhere that it might even be referenced. Still same error. Apparently the conflict is in the way JBoss sets up its parser factory and some dependencies on crimson.jar. I need to run JBoss for ejbs, can't just run Tomcat alone.
Anyone found a way to get Jetspeed to run with JBoss? -----Original Message----- From: Santiago Gala [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 12, 2001 8:00 AM To: Jetspeed Users List Subject: Re: Jetspeed release 1.3a2 candidate John Wooten wrote: >Why does this keep getting released with a set of instructions that say, >drop the jetspeed war file into the tomcat webapps and then start the server >and it will work? > >Once again, I did that. >I then connected to Jetspeed via the browser, logged in as turbine, turbine. >Got logged in. Then chose Customize and got the same page as after logging >in. NO CUSTOMIZATION. > You have an older jaxp parser (probably an older xerces version, or crimson.jar or parser.jar) in your classpath, and it is used instead of the JAXP version included in Jetspeed. Please clean your classpath of older versions. For tomcat 3.2.X the simplest way is to remove parser.jar from the tomcat/lib directory, and put there a copy of the xerces.jar that comes with jetspeed. Until people migrates to tomcat 4, where classpath isolation effectively works, this will be a nightmare. Not sure about 3.3 > >LOG STILL READS: >jetspeed.portalfactory - /WEB-INF/psml/default.psml >[Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Initializing the PortletFactory >[Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Returning local cached URL >[Mon Dec 10 09:50:12 EST 2001] -- ERROR -- > Exception: java.lang.AbstractMethodError > Stack Trace follows: > java.lang.AbstractMethodError > at >org.exolab.castor.xml.UnmarshalHandler.startElement(UnmarshalHandler.java:6 6 >3) > at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1335) > at >org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValida t >or.java:840) > at >org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScann e >r.java:1852) > at >org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(X M >LDocumentScanner.java:1233) > at >org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner . >java:380) > at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:908) > at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:335) > at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:267) > at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:388) > at >org.apache.jetspeed.xml.api.portletmarkup.Portlets.unmarshal(Portlets.java: 4 >52) > at >org.apache.jetspeed.portal.factory.PortletSetFactory.init(PortletSetFactory . >java:230) > >--------PLEASE NOTE. This was reported as a problem over a week ago. NO >ANSWER AS TO HOW TO FIX, WHERE TO LOOK, OR A WORK AROUND. NEW RELEASE STILL >DOES EXACTLY THE SAME THING AS BEFORE> > >OBVIOUSLY THERE IS A SETUP PROBLEM. WHAT ELSE IS NECESSARY TO GET THIS TO >WORK? IS THERE A PIECE OF INFORMATION MISSING? DOES SOMETHING ELSE NEED TO >BE INSTALLED OTHER THAN JUST DROP THE WARFILE INTO THE WEBAPPS AND IT WILL >WORK? > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
