Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Library Conflict Involving BCEL Library

Library Conflict Involving BCEL Library

2006-09-06       - By Erin Harris
Reply:     1     2     3     4     5     6  

Hi Edwin,

Are you using a JDK that ships Xalan?  If not, then you don't need to use
the endorsed directory.  The endorsed directory is only needed if Xalan is
shipped as part of the JDK and you want to use a different version of
Xalan.  If the JDK you are using does ship Xalan then is it not at the
level that you need?

Thanks.


Erin Harris




"Edwin Lee" <edwinlee.11@(protected)>
06/09/2006 05:56 AM

To
xalan-j-users@(protected)
cc

Subject
Library Conflict Involving BCEL Library






Hi guys,

i'm having an issue here which is not exactly an issue with Xalan itself,
but its due to the BCEL library that Xalan comes bundled with, so am
wondering if anyone has faced this before.

The background is that i'm running WebLogic Server 8.1 (on JDK 1.4).

i need to deploy two web applications (WAR) on the app server.

In web application 1,
i need to make use of Xalan, and since i'm running JDK 1.4, i'll have to
override the endorsed standards by placing serializer.jar, xalan.jar,
xercesImpl.jar and xml-apis.jar in the JDK endorsed directory. Now, the
xalan.jar comes bundled with the BCEL package, which is, according to the
manifest, BCEL version 5.0 rc1.

In web application 2,
the problem is that here, there is a dependency on BCEL version 5.1. Now
even though this web application has its own copy of bcel.jar in its
WEB-INF/lib, the VM (rightly) loads from the BCEL package in the endorsed
directory. This caused a NoSuchMethodError when trying to execute one of
the methods in the BCEL package. (i looked up the source for BCEL 5.0 rc1,
and indeed the method was not in that version.)


Has anyone ever experienced this? How do you get around it?



Thanks in Advance,
Edwin



<br><font size=2 face="sans-serif">Hi Edwin,</font>
<br>
<br><font size=2 face="sans-serif">Are you using a JDK that ships Xalan?
&nbsp;If not, then you don't need to use the endorsed directory. &nbsp;The
endorsed directory is only needed if Xalan is shipped as part of the JDK
and you want to use a different version of Xalan. &nbsp;If the JDK you
are using does ship Xalan then is it not at the level that you need?</font>
<br>
<br><font size=2 face="sans-serif">Thanks.</font>
<br><font size=2 face="sans-serif"><br>
<br>
Erin Harris<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Edwin Lee&quot; &lt
;edwinlee.11@(protected)&gt;</b>
</font>
<p><font size=1 face="sans-serif">06/09/2006 05:56 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">xalan-j-users@(protected)</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Library Conflict Involving BCEL Library<
/font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=3>Hi guys,<br>
<br>
i'm having an issue here which is not exactly an issue with Xalan itself,
but its due to the BCEL library that Xalan comes bundled with, so am wondering
if anyone has faced this before.<br>
<br>
The background is that i'm running WebLogic Server 8.1 (on JDK 1.4).<br>
<br>
i need to deploy two web applications (WAR) on the app server.<br>
<br>
In web application 1,<br>
i need to make use of Xalan, and since i'm running JDK 1.4, i'll have to
override the endorsed standards by placing serializer.jar, xalan.jar,
xercesImpl.jar
and xml-apis.jar in the JDK endorsed directory. Now, the xalan.jar comes
bundled with the BCEL package, which is, according to the manifest, BCEL
version 5.0 rc1.<br>
<br>
In web application 2, <br>
the problem is that here, there is a dependency on BCEL version 5.1. Now
even though this web application has its own copy of bcel.jar in its WEB-INF
/lib,
the VM (rightly) loads from the BCEL package in the endorsed directory.
This caused a NoSuchMethodError when trying to execute one of the methods
in the BCEL package. (i looked up the source for BCEL 5.0 rc1, and indeed
the method was not in that version.)<br>
<br>
<br>
Has anyone ever experienced this? How do you get around it?<br>
<br>
<br>
<br>
Thanks in Advance,<br>
Edwin<br>
</font>
<br>