Please don't do a forceExpand.
The point of the OMSourcedElement is to improve performance by preventing a
forceExpand.
Can you write an axiom unit test which demonstrates the problem. Perhaps
you will recognize a solution after writing the testcase.
Thanks,
Rich Scheuerle
IBM Web Services
Apache Axis2 ([EMAIL PROTECTED])
512-838-5115 (IBM TL 678-5115)
"Nandana
Mihindukulasooriy
a" To
<[EMAIL PROTECTED] [email protected]
l.com> cc
10/20/2008 09:00 Subject
AM [AXIOM] Attaching
OMSourcedElementImpl as a child
Please respond to
[EMAIL PROTECTED]
ache.org
Hi Devs,
I have a service which does JSON to SOAP conversion. Service code is
follows.
MessageContext outMsgCtx =
MessageContext.getCurrentMessageContext().getOperationContext
().getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
outMsgCtx.setProperty(Constants.Configuration.MESSAGE_TYPE,"text/xml");
//System.out.println(param.toString());
return param;
Param element is an OMSourcedElementImpl with a JSONDataSource. The problem
occurs when attaching this element to the response envelope in the message
receiver. In the setComplete method when deattaching we make the data
source
null without expanding it. This doesn't cause a problem when we really
removing the element but when we adding this as a child to another document
this causes a problem. Shall we forceExpand() to solve this problem or is
there a better solution ?
thanks,
nandana
