The idea would be to implement the necessary changes in Axiom, Axis2 and Synapse so that DOOM can be used end-to-end for the messages that flow through Axis2 and Synapse. That has potential benefits for scenarios that use WS-Security (because it avoids LLOM <-> DOOM transformations in Rampart) or mediators that interact with frameworks that support DOM.
Of course, both Axis2 and Synapse use the Axiom API and not LLOM directly, so one would expect that to work, but that is only theory. E.g. in earlier Axiom releases, there was a major difference between LLOM and DOOM with respect to the lifecycle of the OMFactory instances, that made it virtually impossible do substitute LLOM with DOOM without major code changes. This was only changed in the last Axiom release (see AXIOM-412). The missing OMSourcedElement support in DOOM is another issue. There are likely lots of other places where Axis2 or Synapse depends on behavior specific to LLOM. Andreas On Tue, Apr 2, 2013 at 7:12 PM, Udayanga Wickramasinghe <[email protected]> wrote: > Hi Isuru, > Synapse already supports Axiom API which i think DOOM is a part of. What > exactly do you mean by "Axiom DOOM Support for Synapse" ? > Regards, > Udayanga > > > On Tue, Apr 2, 2013 at 4:35 AM, Isuru Ranawaka <[email protected]> wrote: >> >> Hi All, >> >> I am an undergraduate student of Computer Science and Engineering >> department University Of Moratuwa. I would like to do a project for GSOC . >> One idea is to Axiom DOOM Support for Synapse. Is that idea is good enough . >> >> thanks >> isuru > > > > > -- > http://www.udayangawiki.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
