DO NOT REPLY [Bug 15447] New: - p = new DOMParser(); creates an UnsatisfiedLinkError

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15447>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15447

p = new DOMParser(); creates an UnsatisfiedLinkError

           Summary: p = new DOMParser(); creates an UnsatisfiedLinkError
           Product: Xerces2-J
           Version: 2.2.1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: DOM
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: Jkubitschek@intershop.com


I'm working on an VisualJ++ Project which creates an executeable including the xerces 
packages.
Since i have switched from Xerces 1.4 to 2.2.1 my Application won't start.
I 
debugged and found the cause of this error here 

=> parser = new DOMParser();

at this point 
i get the following exception:

Could not initialize.
java.lang.UnsatisfiedLinkError: 
java/security/AccessController.doPrivileged  Possible causes: If you are trying to use 
J/Direct(@dll.import), check your compiler version(for JVC, requires 4336 or greater.) If you 
are trying tu use RNI, there are new requirements: see documentation.
at 
java/sevurity/AcessController.doPrivileged(AccessController.java)
at 
org/apache/xerces/util/SecuritySupport12.getContextClassLoader
at 
org/apache/xerces/util/ObjectFactory.findClassLoader
at 
org/apache/xerces/util/ObjectFactory.createObject
at 
org/apache/xerces/util/ObjectFactory.createObject
at 
org/apache/xerces/parsers/DOMParser.<init>
at 
org/apache/xerces/parsers/DOMParser.<init>
...etc.

the same Application with the 
same code worked fine before i switched to Xerces 2.2.1.
Until now i've seen this error only on 
some NT4SP6 machines. Other machines works perfekt also with the new package. On win2k machines 
i've never had this Problem.
Could you please thell about the changes between 1.4 & 2.2.1 that 
could cause this problem on some NT4 machines?

Thank you.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org