OpenSAML user discussion

[Chad La Joie <>]

As I already said.  No.

The current code uses JAXP 1.3 and DOM 3 all over the place.  Those were 
the standards we chose to use.  Have you checked how to use the 
classloading mechanisms in WebSphere to isolate the JAXP 1.3 and DOM 3 
classes from those used by the application container?  If not, you 
probably should.

Sunit Randhawa wrote:
> Scott,
>
> Is there a possibility to refactor the openSAML code using JAXP1.2 which
> again would not depend on DOM3?
>
> Thanks,
> Sunit.
>
> -----Original Message-----
> From: Scott Cantor [mailto:] 
> Sent: Thursday, July 27, 2006 1:51 PM
> To: Sunit Randhawa
> Cc: 
>
> Subject: RE: OpenSAML dependency on DOM3
>
> > I wanted to know what is the specific code in OpenSAML that 
> > is dependant on Dom 3 API which otherwise not available in 
> > DOM 2. And if there is a possibility to modify the OpneSAML 
> > code to use DOM2 instead.
>
> ID attribute stuff. Build without it, not hard to find all the
> dependencies.
> Doesn't really matter because you also need JAXP 1.3, and that's going
> to
> break you at least as badly, and there's no way you're avoiding that
> part.
>
> > Our application runs on WAS 5.1 which is still not supporting 
> > DOM3 and if we put DOM3 in endored directory then some of WAS 
> > related functions breaks.
>
> What could possibly break? I would suspect it's JAXP 1.3 that's breaking
> it,
> not the DOM version. DOM3 is a superset of DOM2.
>
> -- Scott

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