XOP activation

Hi all, I am a newbie on Axis2. I have created an example using MTOM which runs successfully. My problem is the attachment is included in the soapBody. I know that xop allows to put the attachment outside of the SOAP enveloppe (is that correct ?). Can you explain me how I can activate xop in

Re: Axis 1.4, style=message

done https://issues.apache.org/jira/browse/AXIS-2573 Thanks Anne Thomas Manes wrote: Please file a JIRA. On 10/18/06, Charles Souillard <[EMAIL PROTECTED]> wrote: Hi all, does anybody have an idea ? Thanks Charles Charles Souillard wrote: > Hi all, > > I am using axis 1.4. I

Re: Axis 1.4, style=message

Hi all, does anybody have an idea ? Thanks Charles Charles Souillard wrote: Hi all, I am using axis 1.4. I want to deploy a new WS using message style. To do that, I execute wsdl2java tool with the following options : -s -a -B -H Then I replace the implementation file by one compliant with

Axis 1.4, style=message

Hi all, I am using axis 1.4. I want to deploy a new WS using message style. To do that, I execute wsdl2java tool with the following options : -s -a -B -H Then I replace the implementation file by one compliant with message style : public Element[] validationRequest (Element[] bodies) throws E

Re: document/literal multiParts outMessage

document/literal but still want a programming model that simulates the RPC style (so that you can still invoke the method using parameters rather than using a wrapped object), then use the "wrapped style. See http://atmanes.blogspot.com/2005/03/wrapped-documentliteral-convention.html.

document/literal multiParts outMessage

Hi all, this is a general question about the Axis (1.4) use. I am trying to execute an example with a simple message as input with only one part : I have a more complex output message having two parts : I am using the document style and the literal use for this operation. When

[AXIS 1.4] soapenc:array

Hi all, I am using Axis for 3 years and I am falling down a very specific case. I am trying to call a WS having a particular complexType as an output part type : wsdl:arrayType="tns:GeocoderResult[]"/> When I

Re: [Axis2 1.0][Sandesha2] Problem connecting server RMSampleService

Hi all, I am trying to use the same example. I am encoutering the same problem. I have also caught the http request inside tcpmon. You can find it hereafter : POST /axis2/services/RMSampleService HTTP/1.1 User-Agent: Axis2 SOAPAction: http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence Hos

Re: Attachment use in the WS skeleton

Thank you !!! using LABEL_IN_VALUE is coreect !! Then in my client file, I only have to perform the following code and the image is created on my hard disk ! OMElement xop = (OMElement)imageEl.getFirstOMChild(); OMAttribute attr = xop.getAttribute(new QName("href")

Re: Attachment use in the WS skeleton

Could you help me ? Thanks a lot Charles Charles Souillard wrote: Hi, you can find in attachment the client, the wsdl and the skeleton files. Thanks a lot for your help. Charles Charles Souillard wrote: Hi, I have added the enable mtom property(true) I still have an error. Which code

Re: Attachment use in the WS skeleton

Hi, you can find in attachment the client, the wsdl and the skeleton files. Thanks a lot for your help. Charles Charles Souillard wrote: Hi, I have added the enable mtom property(true) I still have an error. Which code should I execute in the skeleton when this property is enabled ? With

Re: Attachment use in the WS skeleton

on you are asking a DataHandler from a non-binary node.. You can use the TCPMON to see how your attachment is going... See whether it goes as a MIME part or as base64.. Thanks, ~Thilina On 5/12/06, *Charles Souillard* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

Attachment use in the WS skeleton

Hi all, I am using Axis 2 1.0 on a Linux computer for 2 weeks. I am using Sun jdk1.5.0_06. I am able to call a simple Helloworld WS using xmlbeans DataBinding. I haven't modified axis2.xml configuration. Axis 2 web app is deployed into my Tomcat 5.5.15. I am now trying to add an attachment i