You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Alfredo Scotto (JIRA)" <xa...@xml.apache.org> on 2006/09/19 00:50:22 UTC
[jira] Commented: (XALANJ-1402) Incorrect usage of context
ClassLoader for static field initialization
[ http://issues.apache.org/jira/browse/XALANJ-1402?page=comments#action_12435602 ]
Alfredo Scotto commented on XALANJ-1402:
----------------------------------------
Right, probably there are more places you listed. I just opened a bug because when after I deployed my application, with xalan/xerces 2.7.1, on Websphere 6.0 its deployment manager will not work anymore and there are no way to deploy new applications. It's look like it starts to use the classes from my application and I know (because I tried to put those jars in endorsed) they are not good for WAS6.0.
I also experienced strange problems with Eclipse with plugins using different version of xalan/xerces. I pointed to buggy plugin but now I know the problem is from our two X-guys.
>From what I saw there is same kind of "class finder" like the one in common-logging. It probably looks to much and without boundaries, just to create problems.
> Incorrect usage of context ClassLoader for static field initialization
> ----------------------------------------------------------------------
>
> Key: XALANJ-1402
> URL: http://issues.apache.org/jira/browse/XALANJ-1402
> Project: XalanJ2
> Issue Type: Bug
> Components: Xalan
> Affects Versions: 2.5
> Environment: Operating System: All
> Platform: All
> Reporter: Igor Malinin
> Assigned To: Xalan Developers Mailing List
> Priority: Critical
> Attachments: patch-static.txt
>
>
> Several classes read resources through thread context ClassLoader. When it is
> right thing for factories, it it is definitely not right for static field
> initialization. Due to this it is problematic for me to use Xalan as Eclipse
> plugin. This might be issue in other environments with many ClassLoaders too.
> These two classes should not use context Classloader:
> org.apache.xalan.serialize.Encodings
> org.apache.xalan.templates.OutputProperties
> Instead they should simply read properties from their OWN Classloader as
> org.apache.xalan.serialize.CharInfo does:
> ClassLoader cl = CharInfo.class.getClassLoader();
> There are one more class:
> org.apache.xalan.processor.TransformerFactoryImpl
> It does "System.setProperties(systemProps)" in it's static initialization!
> Actually it does'nt set anything what could be needed except sax-driver (which
> should be defined in META-INF/services by default!), and I think it is something
> from legacy code and must be removed now (to remove possible side effects)...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org