You need to take into account that Axis2 by default doesn't preserve CDATA sections (and converts them to text nodes). You can use the approach described in [1] to change this.
Andreas [1] http://people.apache.org/~veithen/synapse/faq.html On Wed, Aug 12, 2009 at 00:39, Ramya K Grama<[email protected]> wrote: > Hello, > I'm using Axis2/Java to create a web service wherein the request and > response xmls are very much the same except for some additional data from > the db that gets added on to the request as a response. > Also, there is a lot of CDATA sections in the request that need to be sent > back in the response as is without any modification. > > In designing this service, we've come up with the strategy of saving the > incoming SOAP request.xml(in memory) somewhere so that it can be used to > recreate the response + updated data from the db (stuffing in empty tags > with data from db). > > Is this a good approach as far as Axis2 is concerned. If so what/how would > be teh best place of storing the request.xml. Are there any multi-threading > issues that i need to be concerned about. What would be a fool-proof and > optimal approach of doing this in Axis2. > > From my initial research, I've found that OperationContext with SOAPSession > scope can be used for this. Am I correct here? > > Also, since there are a lot of CDATA sections in the request and response > xmls, is there anything special that needs to be done? > > Your feedback will be very helpful in designing my service further. > > Thanks, > wsNewbie.
