Re: Strange problem with BSFManager (maybe OS X only)

[Bradley Wagner]

I have found a few links about this on the web.

http://lis​ts.apple.c​om/archive​s/java-dev​/2008/Apr/​ 
msg00078.h​tml
http://doc​s.sun.com/​app/docs/d​oc/820-629​6/ghmay?a=​view
http://blo​g.springso​urce.com/a​rjen/archi​ves/2006/0​ 
9/24/14com​patibility​jar-in-app​le-jdk-15/

All of them seem to suggest that deleting this JAR is ok, except that  
my app is an installed app and I don't really want to ask my OS X  
clients to all do that as part of the upgrade.

Others seem surprised that this JAR is getting loaded given that there  
is a Xalan JAR in my webapp's classpath because apparently this  
14compatability JAR is always loaded at the end of the classpath. I  
might try cross-posting on the Apple Java mailing list to see if they  
have any suggestions.

- Bradley

On Nov 20, 2008, at 2:31 PM, Bradley Wagner wrote:

And thanks again, for some reason, it's trying to load the  
TransformerFactoryImpl class which is in my Xalan JAR from:
[Loaded org.apache.xalan.processor.TransformerFactoryImpl from file:/ 
System/Library/Frameworks/JavaVM.framework/Versions/A/ 
Resources/.compatibility/14compatibility.jar]
I'm definitely running Tomcat with Java 5, but wondering if this is  
some problem with the way we compiled the Xalan JAR from source. We  
used these directions: http://xml.apache.org/xalan-j/downloads.html#buildmyself

Thanks,
Bradley

On Nov 20, 2008, at 2:05 PM, Gary L Peskin wrote:

A classloader trace should show where the Xalan jar is being loaded  
from.
This is enabled via the -verbose:class switch.

Gary

-----Original Message-----
From: Bradley Wagner [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 10:59 AM
To: Gary L Peskin
Cc: xalan-j-users@xml.apache.org
Subject: Re: Strange problem with BSFManager (maybe OS X only)

Wow, thanks very much... you're exactly right:

java.class.path=/Users/bradley/Java/apache-tomcat/bin/bootstrap.jar
version.JAXP=1.1
java.ext.dirs=/Library/Java/Extensions:/System/Library/Java/
Extensions:/System/Library/Frameworks/JavaVM.framework/Versions/ 
1.5.0/
Home/lib/ext
version.xerces2=Xerces-J 2.9.0
version.xerces1=not-present
version.xalan2_2=Xalan Java 2.4.1
version.xalan1=not-present
version.ant=not-present
java.version=1.5.0_16
version.DOM=2.0
version.crimson=present-unknown-version
sun.boot.class.path=/System/Library/Frameworks/JavaVM.framework/
Versions/1.5.0/Classes/classes.jar:/System/Library/Frameworks/
JavaVM.framework/Versions/1.5.0/Classes/ui.jar:/System/Library/
Frameworks/JavaVM.framework/Versions/1.5.0/Classes/laf.jar:/System/
Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/ 
jsse.jar:/
System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/
jce.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/
Classes/charsets.jar
version.SAX=2.0
version.xalan2x=Xalan Java 2.4.1

It appears it's using Xalan 2.4.1 somehow. The strange thing is that
all we really did was upgrade the Xalan JAR from 2.6 to 2.7.1. I  
also
have yet to find any alternate xalan implementations in any of the  
JAR
files or directories mentioned above.

I'll keep looking and post back here if I find anything.

Thanks again,
Bradley