Neethi Thoughts...

[Dan Diephouse <da...@envoisolutions.com>]

Hi all,

I thought I'd just pass along a quick little intro I wrote to Neethi and
also some feedback we had as CXF.
http://netzooid.com/blog/2007/04/26/ws-policy-with-apache-neethi/

To quote the relavent part for discussion:
--

Neethi also includes an AssertionBuilder class which builds these assertions
from AXIOM elements. As we're trying to reduce the amount of dependencies
needed for CXF, we opted to create our own version of the AssertionBuilder
class which uses DOM elements instead. We have a few implementations of the
AssertionBuilder floating around, but one of the most interesting is
probably the JaxbAssertionBuilder. This builder can build an assertion from
a JAXB object. This makes it trivial to add new assertions. Just write your
schema, generate your JAXB beans, and tell CXF to look for the new assertion
builder.

All in all, I'm pretty pleased with the model Neethi has given us. If I
could change one thing though, I would separate out the AXIOM dependant
interfaces into a separate package. And similarly with the DOM
implementations that we've written. However at this point (post
2.0release), I don't think its really possible so I haven't brought it
up.
--

I know there probably isn't much we can do about the axiom dependency now,
but there were some comments that I saw in JIRA about introducing an AXIOM
dependency into the policy components themselves. I wanted to send this
along to say "please no!" :-)

Cheers,
- Dan
-- 
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog