>> Removing the packages fron the jars was how I got round my WL issues - a >> bit of a pain - but it did the trick.
Oh? I just changed the classpath in the startWeblogic.sh script so that the xml-apis.jar and xerces-?.jar where in the classpath before the weblogic.jar file, and that stopped the NoSuchMethod thingy. I am rather against messing with BEA JAR files (I think it breaches the contract doing so, and therefore no support). I read the FAQ, and that PJA library is a godsend - because I got the error with X11, and after installing PJA according to the FAQ, cocoon started without any problems at all, and now I can get going on the fun stuff! :) Thanks for all your help folks. Chris. -----Original Message----- From: Anthony Aldridge [mailto:[EMAIL PROTECTED]] Sent: Friday, April 26, 2002 3:56 PM To: [EMAIL PROTECTED] Subject: Re: The woes of Weblogic 6.0sp2 and Cocoon - found the problem at last :) Removing the packages fron the jars was how I got round my WL issues - a bit of a pain - but it did the trick. Tony Konstantin Piroumian <[EMAIL PROTECTED]> on 04/26/2002 02:49:06 PM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: The woes of Weblogic 6.0sp2 and Cocoon - found the problem at last :) Hi > > good news and bad news - > ... > > Note that the class expects there to be a method 'getXMLReader' available in > the SAXParser object (javax.xml.parsers.SAXParser) - this is logical, > because in > the version of Xerces Cocoon was built against, this method exists. > > I then looked at the structure of the SAXParser class that Weblogic 6.0 SP2 > uses, and found out that there is no 'getXMLReader' method!!! > > So who is to blame? > > Well, the offender is BEA - their JAXP API is broken, because it does > not comply with the defacto standard, the one in the Java 1.4.0 API - > whereas > Avalon itself is completely justified in expecting the getXMLReader > method, because it *should* be there according to Sun's API docs. > > Oh well, I'll have to work out how to bypass BEA's XML crud until a new > service pack comes out for 6.0, I guess.... pffff.... You can try to place Xerces and Xalan in weblogic6.1/lib and rename them to something like a_xerces.jar and a_xalan.jar. Also you can try to remove certain packages (org.apache.**) from weblogic.jar and xmlx.jar archives. -- Konstantin > > Thanks to all the folks who tried to help me with my problem :) > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
