Hi Igor:
I'm trying to use Axis2 for dispatching and invoking web services, while
substituting my own XML parser/serializer/object model in place of AXIOM.
I'm not sure I understand what you're trying to do here. All the Axis2
components are built in terms of AXIOM, and the "dispatching and
invoking" parts are all based on being able to use AXIOM to get at
either the SOAP headers or the SOAP body. Plus the Handler framework
requires the messages to be in terms of AXIOM so that common code to do
reliability/security/etc can be plugged in in a universal way. AXIOM
itself can "get out of the way" for body processing (see recent
DataBinding discussion, for instance) by letting you at the
XMLStreamReader directly. But because it's AXIOM, we also have the
ability to *tell* if anyone in the processing pipeline needs the whole
OM to be built (for instance security) - in that case you can still use
code that's been written in terms of XMLStreamReader, but behind the
scenes AXIOM also makes the in-memory model.
In short, AXIOM is really pretty core to the way Axis2 works, and that
seems like goodness to me.
What scenarios are you trying to enable?
Thanks,
--Glen
