I had problems with Xalan and Weblogic Portal 8.1 quite a while ago. Xalan started including XSLTC in xalan.jar. XSLTC uses bcel and a couple other classes that are also used by Weblogic Portal's "Java Page Flow". When xalan.jar was put in java's lib/endorsed the portal would not start. Without it, the JDK 1.4 default version of xalan was used which would cause Cocoon to have problems. The Xalan team ended up creating two versions so that lib/endorsed could be safely overridden, but the XSLTC part is still a problem.
I would suggest that someone open a bugzilla report with them and get them to create a version without the dependent jars. Ralph -----Original Message----- From: Gianugo Rabellino [mailto:[EMAIL PROTECTED] Sent: Monday, March 29, 2004 11:47 AM To: [EMAIL PROTECTED] Subject: Re: extra bcel jar Joerg Heinicke wrote: > On 29.03.2004 19:47, [EMAIL PROTECTED] wrote: > >> Remove the bcel classes from the xalan.jar and >> create an extra jar for those. > > > *Ouch*. If I understand this correctly we have to do it for every update > on the Xalan jar until our continuations stuff goes into bcel that goes > later on into Xalan jar? Hopefully we will never forget it! Well, at a very least everything is under the ASL and in sync now... wouldn't Gump be able to spot the problem if we miss a cycle? Ciao, -- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Blogging at: http://www.rabellino.it/blog/)
