This is not done because of the flexibility and the way people use Axiom API.
Axiom allows adding arbitrary nodes to a AXIOM tree without those nodes having to be imported or having to be in the same document. But in DOOM case this doesn't work. This is because DOM requires all nodes in a tree to belong to the same document and any alien nodes to be imported into the document before appending them to the tree. If we change the AXIOM impl after security processing then we will have to set DOOM as the effective impl for that AXIS2 instance as well. In that case we will not be simply able to create a new OMFactory and append elements created with that to another AXIOM tree. See the use of org.apache.axis2.receivers.RawXMLINOutMessageReceiver in quickstartaxiom sample in Axis2. Thanks, Ruchith WALTON Jason wrote: > I was just wondering; in the inflow, Rampart converts the LLOM-based OM > model to a DOOM model, so Rampart can pass the DOOM based model, which > supports the DOM interfaces, into WSS4J. But then, why convert the DOOM > model back to LLOM? Why not just leave it as DOOM? The DOOM model > implements the Axiom API, so why would it work any differently than > LLOM? >
signature.asc
Description: OpenPGP digital signature
