[ http://nagoya.apache.org/jira/browse/XALANJ-1707?page=history ]
Jeff Turner updated XALANJ-1707:
--------------------------------
Description:
On jdk >=1.2 (but <1.4) xalan uses the ContextClassLoader to load classes of
its own distribution. This is never appropriate and will lead to
ClassCastException in a J2EE setting.
For loading classes of its own distribution, the (current) ClassLoader that has
loaded the distribution classes (i.e. xalan.jar) should be used.
Glory Details:
--------------
The problem shows up when there is a (outdated) xalan in your (ClassLoader)
path but you want to use a newer version of xalan in your application. Note
that this is NOT an obscure setting but the normal case in every J2EE (1.3)
application because you are guarantied to have JAXP XML access, but often to an
outdated product (in my case I'm using IBM WAS 5.0.1 on Solaris).
In principle the problem is the same as reported for xerces
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24244 . This is because the
offending class is the same in both distributions:
org.apache.xml.utils.ObjectFactory.
Environment:
Operating System: Other
Platform: Other
was:
Operating System: Other
Platform: Other
Bugzilla Id: (was: 24245)
Restoring description.
> Use of ContextClassLoader is not appropriate
> --------------------------------------------
>
> Key: XALANJ-1707
> URL: http://nagoya.apache.org/jira/browse/XALANJ-1707
> Project: XalanJ2
> Type: Bug
> Components: Other
> Versions: 2.5
> Environment: Operating System: Other
> Platform: Other
> Reporter: Thomas Pasch
> Assignee: Xalan Developers Mailing List
>
> On jdk >=1.2 (but <1.4) xalan uses the ContextClassLoader to load classes of
> its own distribution. This is never appropriate and will lead to
> ClassCastException in a J2EE setting.
> For loading classes of its own distribution, the (current) ClassLoader that
> has
> loaded the distribution classes (i.e. xalan.jar) should be used.
> Glory Details:
> --------------
> The problem shows up when there is a (outdated) xalan in your (ClassLoader)
> path but you want to use a newer version of xalan in your application. Note
> that this is NOT an obscure setting but the normal case in every J2EE (1.3)
> application because you are guarantied to have JAXP XML access, but often to
> an
> outdated product (in my case I'm using IBM WAS 5.0.1 on Solaris).
> In principle the problem is the same as reported for xerces
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24244 . This is because the
> offending class is the same in both distributions:
> org.apache.xml.utils.ObjectFactory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
