> > IMHO, cloning is not a use case that we really need for a SOAP engine. > If you are trying to use the same XML over and over again, passing it > here and there, without modification, you are really routing stuff and > not doing that many business logic processing. > I am still trying to figure out why would one want to detach and attach > a node in a module or a service. If the use case is less than 10%, I do > not think it is a good idea to major changes to the current AXIOM > implementation that works. > > Samisa... > > Hi,
I raised the particular issue based on a way of coping a portion of a XML tree using axiom in order to solve my real requirement.( And it can be solved using the normal serialize/desterilize approach that Samisa mentioned and I just wanted to clarify that, is there a in-built way provided by axiom). I agreed with Samisa, that the use case may be fairly in-frequent and therefore we may not need this as an in-built functionality to axiom. And my use case is quite similar to a case where we have a client and two services. So, what that client does is it sends a request to a particular service (A) and get a response and extract a portion of it (based on qname) and attach it to the request that is going to made to the second service (B). Also I don't want to do any modification to the extracted part but have to be conscious about the namespaces. [My use case is similar to this but it is not exactly the same. The real scenario is described on WS-SecurityPolicy Appeddix B [1]]. Thanks, Kasun. [1] http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf
