Library Conflict Involving BCEL Library 2006-09-07 - By Edwin Lee
BTW, there's something that i've tried, please let me know if there are any
potential pitfalls with this.
1. Remove the bcel package (ver 5.0 rc1) from xalan.jar.
2. Add bcel.jar (ver 5.1) to the endorsed directory.
By doing this, web application 2 below (that depends on BCEL 5.1) works fine
now. However, my concern is whether web application 1 (using Xalan) will run
into problems later on (as Xalan is dependent on BCEL 5.0 rc1 instead of 5.1
).
Please let me know, thanks.
Regards,
Edwin
On 9/6/06, Edwin Lee <edwinlee.11@(protected)> wrote:
>
> 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
>
>
BTW, there's something that i've tried, please let me know if there are any
potential pitfalls with this.<br><br>1. Remove the bcel package (ver 5.0 rc1)
from xalan.jar.<br>2. Add bcel.jar (ver 5.1) to the endorsed directory.
<br><br>By doing this, web application 2 below (that depends on BCEL 5.1) works
fine now. However, my concern is whether web application 1 (using Xalan) will
run into problems later on (as Xalan is dependent on BCEL 5.0 rc1 instead of
5.1).<br><br>Please let me know, thanks.<br><br><br><br>Regards,<br>Edwin<br>
<br><br><div><span class="gmail_quote">On 9/6/06, <b class="gmail_sendername"
>Edwin Lee</b> <<a href="mailto:edwinlee.11@(protected)">edwinlee.11@(protected)
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div
>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></div><div><span class="sg">Edwin<br><br>
</span></div></blockquote></div><br>
|
|
