Skip to Content.
Sympa Menu

mace-opensaml-users - Re: can't register schemas

Subject: OpenSAML user discussion

List archive

Re: can't register schemas


Chronological Thread 
  • From: Mintoo C <>
  • To: Scott Cantor <>
  • Cc:
  • Subject: Re: can't register schemas
  • Date: Wed, 16 Mar 2005 17:39:47 -0500
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=GE4mvZOzsoc1P72T0//aq4Oz27ocG83uNWl2UGaAaphX6uijpACf5GvrWA76OfzfP8w2jAXtxvWbN+99Cg6oSSvzmz4+CmmYCWIWJRFo0+N6Nt1ks0wW/enU2oBeUH3uU/QYtHfTdijqWJngN62MtK9wTeKE9ylqwDQOW9tRYdc=

Hi,
I believe it was more of a compatibility issue.
DOM and xerces have been notirious in causing backward compatibility
problems ever since.
Even my eclipse crashes at startup when the endorsed jars are in place.
Strangely, once started, I can then put the jars back in and it works
well thereon.
Thanks
Mintoo C

On Wed, 16 Mar 2005 17:26:43 -0500, Scott Cantor
<>
wrote:
> > 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?
>
> Probably not, but are there actually things that worked in 1.2 that don't in
> 1.3? I would assume Sun would only break apps that were doing evil things
> (like say OpenSAML up to now).
>
> Anyway, I'm very happy with the 1.3 schema stuff, it addresses a lot of
> nasty issues and simplifies life on JDK 1.5 without making 1.4 any worse, so
> I feel pretty happy with the state of that.
>
> -- Scott
>
>



Archive powered by MHonArc 2.6.16.

Top of Page