OpenSAML user discussion

["Scott Cantor" <>]

> First, I'm sorry if I missed an explanation in the past:  I am curious
> about the reasoning behind creating a SOAP library?  Are axis/axis2
> or other efforts inadequate? 

I think a lot of people find them inadequate, but by SOAP library, we're
talking about objects to handle XMLTooling-based manipulation of SOAP
elements of which there are like 5 or so.

Every XML library is a world unto itself because nobody agrees on what the
processing model should be once you get past SAX or DOM. Everybody has their
"framework", us included. Even my old code did, it just wasn't a good one.

Another consideration is portability. Yes, there's an Axis in C++, but
composing C++ XML libraries makes composing Java libraries look easy.

If it's not possible to use the code in conjunction with Axis (or the many
others that exist), and if the reason for that is something to do with this
code, we'll certainly fix it. But use Axis exclusively? I would say not.

As far as whether Shibboleth uses Axis, I don't have the same objection
there, though I don't think anything has changed that would lead to a
reconsideration there.

-- Scott