OpenSAML user discussion

["Peter Gambino" <>]

Yes.

-----Original Message-----
From: Chad La Joie 
[mailto:]
 
Sent: Monday, February 19, 2007 10:50 PM
To: 

Subject: Re: xerces Version Problem

So, to be clear, this is OpenSAML 1.1?

Peter Gambino wrote:
> This may be my confusion then.  I know that we use Xerces2 - Date on our
> xercesImpl Jar is around 5/2006...   Your Jar was date was older In our
app
> we receive this:
>       
> java.lang.AbstractMethodError:
> javax.xml.parsers.DocumentBuilderFactory.setFeature(Ljava/lang/String;Z)V
>       at org.opensaml.XML$ParserPool.<init>(XML.java:490)
>       at org.opensaml.XML.<clinit>(XML.java:118)
>       at org.opensaml.SAMLRequest.<init>(SAMLRequest.java:122)
> 
>             dbf = DocumentBuilderFactory.newInstance();
>             dbf.setNamespaceAware(true);
>             try {
>>> ERROR HERE:
>
dbf.setFeature("http://apache.org/xml/features/validation/schema/normalized-
> value",false);
>                       } catch (Throwable e) {
>                               log.warn("Unable to turn off data
> normalization in parser, supersignatures may fail with Xerces-J: " + e);
>                       }
>             registerSchemas(null);
> 
>>From all the docs I read, it is because NewInstance fails.  I took our
> xercesImpl jar and plugged it in to the endorsed directory in my opensaml
> directory and received the same errors in the unit tests.  That's why I
was
> going down the road of a xerces version issue.
> 
> 
> 
> -----Original Message-----
> From: Scott Cantor 
> [mailto:]
>  
> Sent: Monday, February 19, 2007 10:13 PM
> To: 
> ;
>  
> 
> Subject: RE: xerces Version Problem
> 
>> We have an app deployed in JBoss that needs Xerces2. We are trying to
>> integrate OpenSAML into our application and cannot move forward because
of
>> the version Disparities.  It appears that OpenSAML is built against the
>> first version.  Does anyone have a solution or a port against the newer
>> version of Xerces?
> 
> There are no versions of OpenSAML that use Xerces 1.x. The code itself is
> not Xerces-dependent at all, it *requires* JAXP 1.3. That goes for
> stable/old and the unreleased version in development.
> 
> The common thread is that the only usable JAXP 1.3 parser we know is
Xerces
> 2.x, so in practice it requires that. Could be that other parsers will
work,
> but Sun's won't.
> 
> So, basically, you're confused in some way. Whatever the disparity is, it
> sure isn't the Xerces version.
> 
> -- Scott
> 
> 
> 

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