Skip to Content.
Sympa Menu

mace-opensaml-users - Re: [OpenSAML] PAOS binding

Subject: OpenSAML user discussion

List archive

Re: [OpenSAML] PAOS binding


Chronological Thread 
  • From: Jonathan Tellier <>
  • To:
  • Subject: Re: [OpenSAML] PAOS binding
  • Date: Wed, 15 Dec 2010 20:43:14 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=HFd95g3kHFxPJj0STRmvsLXMBw7TZpvJoPxmLOifOR7Br1w8x+Dr9upHaAZbxtviMT tLoWL6+fzdq4jtNgHI5GI4QsEEoMYA855ordhFxXojSPjyJp80yw4Gk/7UB286cG0RsY qcN0SCXVTc8ljZkqHTwAd/L2+vFV619078GRM=
> I can't think of any reason you'd need to do that, so that might be a sign
> of a problem.

Well, here are my major reasons.

- To configure ObjectProviders. This can be achieved programatically,
but isn't cleaner to have them configured in XML files alongside the
other ObjectProviders?

- To define XML schemes.

- There's also this small thing that I corrected in this commit
regarding the HTTPSOAP11Decoder:
http://gitorious.org/java-opensaml-paos/java-opensaml-paos/commit/179353c6788e58eb3f5b696119e5c1df03cab46b.

However, if those reasons are not valid, I'd be happy to be explained
why. That would relieve me of having to maintain a separate opensaml
branch.

Jonathan

Archive powered by MHonArc 2.6.16.

Top of Page