mace-opensaml-users - RE: OpenSAML on Websphere/Solaris
Subject: OpenSAML user discussion
List archive
- From: Sanga Viswanathan <>
- To: "'Scott Cantor'" <>,
- Subject: RE: OpenSAML on Websphere/Solaris
- Date: Mon, 13 Sep 2004 12:20:23 -0700
- Importance: Normal
Thanks Scott.
The IBM java version I see is the following
bash-2.05# java -version
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.4.2_04-b05
20040627)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
IBM Java ORB build orb1420-20040626
XML build Xalan Java 2.4.D1
XML build XmlCommons 1.0
XML build Xerces-J 2.4.0
So they are using Xerces-J 2.4 version. The DOM 3 jar files are also built
from the 2.4 version (dom3-xercesImpl-2.4.0.jar, dom3-xml-apis-2.4.0.jar).
I am hoping that copying the dom3 jars and removing the IBM supplied jars
should be ok since the base version is 2.4 anyways. I will confirm this with
IBM as well.
thanks
Sanga
-----Original Message-----
From: Scott Cantor
[mailto:]
Sent: Monday, September 13, 2004 11:55 AM
To: 'Sanga Viswanathan';
Subject: RE: OpenSAML on Websphere/Solaris
> Has anyone encountered this issue? Is there a better way to
> make this work? Are the dom3 jar files backwards compatible,
> i.e will IBM applications continue to work if I remove their
> xml.jar files?
The DOM3 jars are just Xerces 2.5 with the extra calls implemented. There is
no case that I know of in which the DOM3 version would behave differently
than the base version.
Of course, if the application requires a particular Xerces version, then you
might need to build the DOM3 version of that particular release instead, but
for the most part the SAML code should work with anything fairly recent.
Most incompatibilities are thus a Xerces version issue, not a DOM3 vs. DOM2
question.
-- Scott
- OpenSAML on Websphere/Solaris, Sanga Viswanathan, 09/13/2004
- RE: OpenSAML on Websphere/Solaris, Scott Cantor, 09/13/2004
- RE: OpenSAML on Websphere/Solaris, Sanga Viswanathan, 09/13/2004
- RE: OpenSAML on Websphere/Solaris, Scott Cantor, 09/13/2004
- SAMLSoapBinding.response with exception, Mike Ferraro, 09/17/2004
- RE: SAMLSoapBinding.response with exception, Scott Cantor, 09/17/2004
- Re: SAMLSoapBinding.response with exception, Mike Ferraro, 09/20/2004
- RE: SAMLSoapBinding.response with exception, Scott Cantor, 09/20/2004
- Re: SAMLSoapBinding.response with exception, Mike Ferraro, 09/20/2004
- RE: SAMLSoapBinding.response with exception, Scott Cantor, 09/20/2004
- Re: SAMLSoapBinding.response with exception, Mike Ferraro, 09/20/2004
- RE: SAMLSoapBinding.response with exception, Scott Cantor, 09/17/2004
- SAMLSoapBinding.response with exception, Mike Ferraro, 09/17/2004
- org.xml.sax.SAXParseException: Content is not allowed in prolog, Jason Pedone, 09/20/2004
- Re: org.xml.sax.SAXParseException: Content is not allowed in prolog, Paul Devine, 09/20/2004
- RE: org.xml.sax.SAXParseException: Content is not allowed in prolog, Scott Cantor, 09/20/2004
- RE: OpenSAML on Websphere/Solaris, Scott Cantor, 09/13/2004
- RE: OpenSAML on Websphere/Solaris, Sanga Viswanathan, 09/13/2004
- RE: OpenSAML on Websphere/Solaris, Scott Cantor, 09/13/2004
Archive powered by MHonArc 2.6.16.