OpenSAML user discussion

[Evan Comer <>]

Hi Scott,

Thank you for your reply.

I'm sorry I didn't describe it clearly.

My application used dom2 xml-apis.jar and xercesImpl.jar. To support
opensaml in my application, I put dom3-xml-api-2.4.0.jar and
dom3-xercesImpl-2.4.0.jar in the endorsed directory. Since my
application used some classes which is in dom2 xercesImpl but not in
dom3-xercesImpl, like org.apache.xerces.dom.DOMInputImpl,
org.apache.xerces.xs.* and so on, I have to use both of xercesImpl.jar
and dom3-xercesImpl-2.4.0.jar.

I tried building my application with all of xml-apis.jar,
xercesImpl.jar, dom3-xml-api-2.4.0.jar and dom3-xercesImpl-2.4.0.jar.
It can run. But I haven't used signing function in opensaml which
called the dom3-api setIdAttributeNS(), and signing whould probably be
used in my application in the future.
I mean, the calls of dom3-api are not been executed right now and  the
program can run, but they will be executed some day. What will happen
then?
Would there be any potential confliction between xml-apis.jar and
dom3-xml-api-2.4.0.jar, xercesImpl.jar and dom3-xercesImpl-2.4.0.jar ?


Thank you.

-Evan

On Thu, 17 Mar 2005 10:26:48 -0500, Scott Cantor 
<>
 wrote:
> > If I included the dom2 jar files, and set the dom3 jar files endorsed
> > as well, would there be any confliction? That's to say, can I use dom2
> > and dom3 at the same time in the same project?
> 
> DOM3 support does not break DOM2 applications. I have no plans to change
> anything or reduce the requirements, particular since the code now requires
> JAXP 1.3 anyway. That's much more likely to raise red flags than using a
> DOM3 parser is.
> 
> If your application doesn't run with this Xerces code or with Sun's JAXP
> parser, you probably need to be looking at the application for bugs,
> frankly.
> 
> -- Scott
> 
>