OpenSAML user discussion

[Chad La Joie <>]

The libraries only have to be in the endorsed directory when the JRE has 
busted implementations of the JAXP 1.3 APIs.  You may use other parsers 
as long as they are JAXP 1.3 compliant.  If IBM isn't repackaging Xerces 
though it's questionable whether they have a compliant parser.

Chris Rose wrote:
> I believe it to be the case that IBM is NOT repackaging a version of
> Xerces-J that is suitable.  Moreover, I'm reasonably sure that the
> version they use is required by other parts of the container.
>
> So, is there any other way to inject a different parser source into
> OpenSAML?  Why is it strictly required that the XML parser be in the
> endorsed directory, as opposed to being on the classpath in general?
>
> On Thu, 2006-03-30 at 17:18 -0500, Chad La Joie wrote:
> > And I just realized why XML4J seemed odd to me.  That library became 
> > Apache Xerces-J on February 9th, 1998.
> >
> > http://www.alphaworks.ibm.com/tech/xml4j
> >
> > While this is not the answer you want to hear, I suspect that unless IBM 
> > is repacking Xerces as XML4j (which is quite possible) that you're 
> > client's environment is simply not going to support the OpenSAML library.
> >
> > Chris Rose wrote:
> > > Hi;
> > >
> > > I see this has been mentioned at least once before on this list, but the
> > > resolution described there () is not sufficient for me.  The versions of
> > > the XML libraries shipped with WebSphere Application Server 6.0.2 on
> > > Solaris are:
> > > # /opt/IBM/WebSphere/AppServer/java/jre/bin/java -version
> > > java version "1.4.2_08"
> > > Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.4.2_08-b03
> > > 20050517)
> > > Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
> > > IBM Java ORB build orb142-20050429
> > > XML build XSLT4J Java 2.6.5
> > > XML build XmlCommonsExternal 1.2.04
> > > XML build XML4J 4.3.4
> > >
> > >
> > > The versions with OpenSAML 1.1a are:
> > > # /opt/IBM/WebSphere/AppServer/java/jre/bin/java -versionjava version
> > > "1.4.2_08"
> > > Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.4.2_08-b03
> > > 20050517)
> > > Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
> > > IBM Java ORB build orb142-20050429
> > > XML build Xalan Java 2.4.1
> > > XML build XmlCommonsExternal 1.3.02
> > > XML build Xerces-J 2.7.1
> > >
> > >
> > > Our client is encountering issues with the XML libraries that can be
> > > traced to the fact that we've replaced the default libraries with those
> > > that come with OpenSAML.  Is there anyone on this list that has
> > > implemented a JAAS login module for WebSphere that uses OpenSAML
> > > authentication that can offer some suggestions as to how to accomplish
> > > that?
> > >
> > > Failing that, how can I (safely) change the name of the parser required
> > > by OpenSAML to one that's available in WebSphere?
> > >
> > > Thanks.

--
Chad La Joie             2052-C Harris Bldg
OIS-Middleware           202.687.0124