OpenSAML user discussion

[W Strater <>]

I am currently using the saaj-impl.jar that comes with Sun's Java WS Developer Pack. Some how I doubt it has been coded not to use the version of Xerces that comes with Sun's JDK. So I am in the market for a SOAP library and probably a replacement for SAAJServlet. I started my work in Java 1.4 and want to move to 1.5. The first time I tried the move, I had more issues than time. I know if I do move to 1.5 I will fix some of these issue but not all.

Wes.

----- Original Message ----
From: Chad La Joie <>
To: OpenSAML <>
Sent: Monday, February 27, 2006 7:00:34 PM
Subject: Re: SOAP library

In many cases you can safely replace the version of Xerces used by other
tools as a fair amount of Java code know correctly uses the JAXP and
DOM/SAX interfaces that have been a standard part of the JDK for years.
  I would suggest you try this and if it breaks the SOAP tool you are
using, well you're not worse off and you can revert, but it may fix
things.  It's worth a shot.

Can I ask what SOAP library you're using?  Maybe you said and I just
missed it.

W Strater wrote:
> I am having issues with SAMLAssertions.toDOM and SOAP Messages created
> by the default MessageFactoryImpl. The SOAP Message appears to be using
> a different version of Xerces and causing problems with
> Document.adoptNode. I mention this not because I have a solution yet but
> to make you aware of an issue that may occur depending on how you create
> the SOAP message.
>
> Wes.
>
> ----- Original Message ----
> From: Chad La Joie <>
> To: OpenSAML <>
> Sent: Monday, February 27, 2006 11:18:30 AM
> Subject: Re: SOAP library
>
> Some SOAP stuff may appear in OpenSAML2, I just haven't gotten that far
> yet (that's next week's work).  In all likelihood, if it appears, it
> will rely on another SOAP library and the basic SAML classes and the DOM
> they generate will work with others (assuming the other classes can take
> DOM objects).
>
> I think re-inventing SOAP libraries and tying our implementation to them
> is a bad idea and we should work to avoid it if we can.  It may turn
> out, and I believe this was true in OpenSAML 1, that it just isn't
> feasible without some pretty rough performance hits.
>
> Andreas Åkre Solberg wrote:
>  > We are in the process of evaulating which SOAP library to accompany  
>  > openSAML.
>  >
>  > I have always though that openSAML was totally independent of a soap  
>  > library, interfacing the soap library with a DOM object, XML stream  or
>  > string. But today I was told that openSAML contains a
> SOAP  implementation.
>  >
>  > Diving into the source I found something that looks like a simple  SOAP
>  > implementation. What are the quality of this implementation -  
>  > production ready? To be used with HTTP servlets? Can it be used with  
>  > Apache? Does it scale to tenths and hundreds of simultanous  
>  > transactions?  Is it used in Shibboleth? Does it work with SSL two- way
>  > cert auth? Would you reccomend using this built-in SOAP thing or  
>  > accompany openSAML with axis or JAX-WS? Would you prefer JAX-WS or  axis
>  > together with openSAML.
>  >
>  > Looking into the java-opensaml2 module of opensaml 2.0 I could not  find
>  > much SOAP stuff. Is it left out, or does it exist in the XML  tool
>  > module or in shib?
>  >
>  > To Scott: Thank you very much for earlier very useful replies on this  
>  > list.
>  >
>
> --
> Chad La Joie             2052-C Harris Bldg
> OIS-Middleware           202.687.0124