OpenSAML user discussion

[Jim Cox <>]

For what it's worth, I've been able to get open saml to work in WAS
6.1.0.19.

The container's default xml parser will work.  There is no need to
package xerxes or xalan in web-inf/lib.  Make sure there are no other
parsers that you are packaging in your web app.  Make sure you set
"Classes loaded with application class loader first" on the ear AND the
web module.  (2 places).


I've included a copy of the libs that are in my web-inf/lib.  (Ivy
appended the version number). 


bcprov-ext-jdk15-1.40.jar* 
clickstream-1.0.2.jar* 
com.springsource.javax.annotation-1.0.0.jar* 
commons-codec-1.3.jar* 
commons-collections-3.2.jar* 
commons-configuration-1.3.jar* 
commons-httpclient-3.1.jar* 
commons-lang-2.4.jar* 
ibatis-sqlmap-2.3.4.726.jar* 
jargs-1.0.jar* 
jcip-annotations-1.0.jar* 
jcl-over-slf4j-1.5.8.jar* 
joda-time-1.5.2.jar* 
log4j-1.2.14.jar* 
not-yet-commons-ssl-0.3.9.jar* 
opensaml-2.2.3.jar* 
openws-1.2.2.jar* 
slf4j-api-1.5.8.jar* 
slf4j-log4j12-1.5.6.jar* 
spring-2.5.6.SEC01.jar* 
spring-ldap-core-1.3.0.RELEASE.jar* 
spring-ldap-core-tiger-1.3.0.RELEASE.jar* 
spring-modules-jakarta-commons-0.8a.jar* 
spring-security-acl-2.0.4.jar* 
spring-security-core-2.0.4.jar* 
spring-security-taglibs-2.0.4.jar* 
spring-web-2.5.6.SEC01.jar* 
spring-webmvc-2.5.6.SEC01.jar*  
velocity-1.5.jar* 
xmlsec-1.4.2.jar* 
xmltooling-1.2.0.jar*


 
Good Luck.

-Jim

On Thu, 2009-11-19 at 21:18 +0100, Jochen van Waasen wrote:
> Well, basically they want to send a consultant from the services 
> devision :-)
> 
> They suggested that I upgrade to WebSphere 7.0.0.7 with built-in SAML 
> support ....
> I will try to update my WebSphere 6.1 to the latest fix pack level, 
> maybe this helps.
> 
> Should the org.w3c.dom.Text be in the xalan.jar ?
> 
> Thanks
> Jochen
> 
> Chad La Joie wrote:
> > What was IBM's suggestion for this?
> >
> > Jochen van Waasen wrote:
> >> Hi guys!
> >>
> >> I am really desperate because I can not make opensaml work in 
> >> WebSphere. I guess this is a class loader issue but maybe someone 
> >> knows ...
> >>
> >> My issue is this:
> >> org.w3c.dom.DOMException: WSWS3732E: Error: This DOM 3 API, method 
> >> getWholeText of interface org.w3c.dom.Text, is not supported.
> >> at 
> >> com.ibm.ws.webservices.engine.xmlsoap.dom.impl.DOMTextImpl.getWholeText(DOMTextImpl.java:210)
> >>  
> >>
> >> at 
> >> org.opensaml.xml.io.AbstractXMLObjectUnmarshaller.unmarshallTextContent(AbstractXMLObjectUnmarshaller.java:336)
> >>  
> >>
> >>
> >> I ship all opensaml .jars (plus xalan and xerces) with my enterprise 
> >> application. The classloader for the app is set to APPLICATION FIRST. 
> >> So it should look at the .jars that come with the enterprise 
> >> application first before it tries to load other .jars. I have tried 
> >> the endorsed mechanism of the jre and put in opensaml .jars (plus 
> >> xalan and xerces) jars on the jre level but the error is still the same.
> >>
> >> My code looks like this:
> >>
> >> DefaultBootstrap.bootstrap();
> >> UnmarshallerFactory unmarshallerFactory = Configuration
> >>              .getUnmarshallerFactory();
> >> Unmarshaller unmarshaller = unmarshallerFactory
> >>                .getUnmarshaller(assertionElement);
> >> // The next line produces the exception
> >> Assertion samlAssertion = (Assertion)unmarshaller
> >>                .unmarshall(assertionElement);
> >>
> >>
> >> I need to put something in my classpath so that 
> >> com.ibm.ws.webservices.engine.xmlsoap.dom.impl.DOMTextImpl is not used.
> >> What .jar does the Unmarshaller need?
> >>
> >> Thanks
> >> Jochen
> >