OpenSAML user discussion

["Mike Ferraro" <>]

Walter and Scott,

Thanks for the advice.  I've printed out the Xerces version and supposedly
I'm using 2.6.2:

[ INFO] [13 Aug 2004 14:14:04,818]
java.endorsed.dirs=/u02/app/weblogic/bea812/jdk141_05/jre/lib/endorsed
[Loaded org.apache.xerces.impl.Version from
/u02/app/weblogic/bea812/jdk141_05/jre/lib/endorsed/xercesImpl.jar]
[DEBUG] [13 Aug 2004 14:14:04,820] Xerces version = Xerces-J 2.6.2

I've looked at the loader output and everything seems to be getting loaded
from the endorsed directory:

[Loaded org.w3c.dom.Node from
/u02/app/weblogic/bea812/jdk141_05/jre/lib/endorsed/xml-apis.jar]
[Loaded org.w3c.dom.Document from
/u02/app/weblogic/bea812/jdk141_05/jre/lib/endorsed/xml-apis.jar]
[Loaded org.w3c.dom.Element from
/u02/app/weblogic/bea812/jdk141_05/jre/lib/endorsed/xml-apis.jar]

The strange thing is that even though it says that it loaded the classes
from the endorsed directory, I still get that exception that I'm not using a
DOM3 compatible library.  I just found a FAQ on BEA's website describing XML
tool upgrades.  It specifically states NOT to include the xml-apis.jar file
when upgrading the Xerces and Xalan libraries.  I have no idea why, but I've
logged a case with their support group to try to find out.

Thanks again.  I'll post if I find out the solution to this issue.

Mike

----- Original Message ----- 
From: "Walter Hoehn" 
<>
To: "Scott Cantor" 
<>
Cc: 
<>;
 "'Mike Ferraro'"
<>
Sent: Friday, August 13, 2004 2:00 PM
Subject: Re: xml library issues


> Mike,
>
> To do this, have the script that starts the app server pass "
> -verbose:class" to the JVM.
>
> -Walter
>
> On Aug 13, 2004, at 12:20 PM, Scott Cantor wrote:
>
> >> I added a debug statement just before creating the SAMLSoapBinding
> >> object
> >> that prints out the value of "java.endorsed.dir".  The value points
> >> to the
> >> standard endorsed directory.
> > [snip]
> >
> > I guess WebLogic support would be a logical place to ask the question.
> > Maybe
> > the other thing to suggest would be to try and trace the classloader
> > and see
> > where it is pulling the parser classes from.
> >
> > -- Scott
> >
>