OpenSAML user discussion

[Mintoo C <>]

Hi,
It turned out to be a Catch22.
The SOAP binding component i'm using is dom2/jaxp1.2
(jaxrpc/axis/glue) while the opensaml implementation is dom3/jaxp1.3.
Had to make changes in opensaml XML.ParserPool to make it compatible
with the inhouse environment.
Was there any other way out?
Thanks
Mintoo C

On Wed, 16 Mar 2005 11:33:31 -0500, Scott Cantor 
<>
 wrote:
> > Any ideas why this would happen?-
> 
> It looks like you're using a cvs build, so you're mostly on your own here,
> but my guess would be a JAXP problem.
> 
> It greatly depends on the environment. With 1.5, you should be able to
> mostly just use the built in JAXP code, but you will need Apache Xalan in
> the classpath for xmlsec (but it wouldn't cause this error). For 1.4, you
> have to endorse Xalan and all of the JAXP support files to override the old
> junk.
> 
> It still mostly works like it did before, it just loads the schemas as
> resources from the jar.
> 
> Basically I'd say this is a Java system issue of some sort.
> 
> -- Scott
> 
>