regarding your mentioning of the outTransform not working, could it be
that there is a space in front of the HelloMessage in the value
attribute of your configuration? Your posted message includes the
space and that will be definitely raising an exception. Make sure that
the value attribute is correctly set to
"{http://test.ws.com/}HelloWorld";.I mentioned of the transform based workaround because I replied to another message asking for the transform feature today and somehow my mind was set to the transform feature. But as Dan mentioned, if you could correct the serialization at the source, that would be a better solution. (I mean the correct in compared to the above workaround using the transform feature). regards, aki 2013/8/19 bhaskerhari <[email protected]>: > I am already using the transformfeature inTransformElements. But for > outTransformElements, it did not work. So when I gave the below entry, it > still produces <HelloMessage>Hello.</HelloMessage> instead of > <ns2:HelloMessage xmlns:ns2="http://test.ws.com/";>Hello.</HelloMessage> > > <property name="outTransformElements"> > <map> > <entry key="HelloMessage" value="{http://test.ws.com/} HelloMessage"/> > </map> > </property> > > > And adding package-info.java also does not produce the desired response. If > I specify namespace as well to the package-info.java, then it would add an > extra namespace to the response wrapper instead of the xmlrootelement. > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Namespace-prefix-ns1-is-missing-in-cxf-soap-response-tp5732560p5732669.html > Sent from the cxf-user mailing list archive at Nabble.com.
