if you want to use the jaxws dispatcher approach, you can find a client example in samples/jaxws_dispatch_provider of the CXF distribution. or alternatively at its git repo: https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=distribution/src/main/release/samples/jaxws_dispatch_provider/src/main/java/demo/hwDispatch/client/Client.java;h=63c7ef8dfa22a3ed18366c550b34afc04e64226e
If you only need the body child (i.e., not needing to read the soap headers), you can use the Source mode instead of SOAPMessage. In either way, you can construct the request message directly and feed it to the corresponding constructor/factory to instantiate the request object (Source or SOAPMessage). regards, aki 2014-06-02 15:33 GMT+02:00 neela <[email protected]>: > Hi Aki, > Thanks for the reply. > You are right, But in my case I get input from other system as map. So its > easy for me to validate the name and pass the parameter as list to the > invoke method with operation information. Thats why I chose the > dynamicclient. > > I was not able to find a way to creating full message payload with namespace > info and parameter values. > > If you have idea/sample please share. > > Regards, > Neela > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Reg-Dynamic-Client-invoke-to-return-SoapMessage-tp5744587p5744600.html > Sent from the cxf-user mailing list archive at Nabble.com.
