Does AXIS2 support document-literal-unwrapped webservice?

Hi Devs, I am trying to use Axis2 1.3 to call a WS which is document-literal-unwrapped, i.e. SOAP message BODY should contain multiple children elements as shown below - ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;

RE: Does AXIS2 support document-literal-unwrapped webservice?

:-- sch:BRCH?/sch:BRCH !--Optional:-- sch:USER_GRP?/sch:USER_GRP !--Optional:-- sch:USER_NUM?/sch:USER_NUM /sch:USER_DATA /sch:OPN50 /soapenv:Body /soapenv:Envelope Paul On Thu, Jul 31, 2008 at 12:23 PM, Narayan Dhillon [EMAIL PROTECTED

RE: [jira] Commented: (AXIS2-3128) Axis2 1.2/1.3 xmlBean with MTOM or SwA for Java Client and .net 2.0 and WSE 3.0 Server

Hi Dims, Could you please confirm that Axis2 doesn't support streaming MTOM with JAXB either? That's the impression I got from Ajith's email earlier. Regards, Narayan -Original Message- From: Davanum Srinivas (JIRA) [mailto:[EMAIL PROTECTED] Sent: 13 March 2008 01:50 To:

RE: Axis2 JAXBRI binding and MTOM not working

Hi, I tried a simple web service client with JAXB binding, and noticed that MTOM parts are being in-lined in the soap message as opposed to being XOP attachments. The same client works fine with ADB binding. Is this a known issue? Any pointers on this will be greatly appreciated. Code

Axis 2 and Rampart handlers

Hi, Could some one please help me to understand why org.apache.rampart.handler.WSDoAllReceiver/Sender handlers are deprecated and still configured in rampart-1.3 module.xml? Regards, Narayan * This email is issued by a VocaLink group

RE: Axis2-1.3 - MTOM and Security not working together

Hi, After enabling the WS-Security X509V3 token profile in AXIS-2 1.3 client, I noticed that attachment file is being sent as base64 string as a parameter inside soap envelope mime part. With Security disabled, file is correctly attached as second mime-part outside main soap envelope.