Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 36032 invoked from network); 22 Feb 2005 18:49:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 22 Feb 2005 18:49:28 -0000 Received: (qmail 17941 invoked by uid 500); 22 Feb 2005 18:49:14 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 17927 invoked by uid 500); 22 Feb 2005 18:49:13 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 17914 invoked by uid 99); 22 Feb 2005 18:49:13 -0000 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=HTML_50_60,HTML_CONVERTED,HTML_MESSAGE,HTTP_ESCAPED_HOST X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from evo.phpwebhosting.com (HELO evo.phpwebhosting.com) (69.93.122.30) by apache.org (qpsmtpd/0.28) with SMTP; Tue, 22 Feb 2005 10:49:11 -0800 Received: (qmail 23523 invoked from network); 22 Feb 2005 18:49:08 -0000 Received: from unknown (HELO BORAH) (66.213.166.34) by 2.69-93-122.reverse.theplanet.com with SMTP; 22 Feb 2005 18:49:08 -0000 Message-ID: <009a01c5190f$0b14bf00$830110ac@Technoligence.com> From: "Hollywood" To: References: Subject: Re: Is this a serious bug in string parameter passing to AXIS 1.2RC2? Date: Tue, 22 Feb 2005 12:48:01 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0097_01C518DC.BE5BDBD0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_0097_01C518DC.BE5BDBD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MessageYup, same issue here Christian. The java2wsdl generates a = different WSDL than Axis does when it auto-generates the WSDl. ----- Original Message -----=20 From: Faucher, Christian=20 To: axis-user@ws.apache.org=20 Sent: Tuesday, February 22, 2005 12:42 PM Subject: RE : Is this a serious bug in string parameter passing to = AXIS 1.2RC2? Thomas, I see. I generated my WSDL using java2wsdl, specifying the proper CLI = argument for WRAPPED. I do not use the auto-generated one, which is = sligthly different from the one generated with java2wsdl. I couldn't = get the auto-generated (?wsdl) to bet ".net friendly", but my java2wsdl = one is. Christian Faucher -----Message d'origine----- De : thomas willomitzer [mailto:willo@test.at]=20 Envoy=E9 : mardi, f=E9vrier 22, 2005 13:38 =C0 : axis-user@ws.apache.org Objet : Re: Is this a serious bug in string parameter passing to = AXIS 1.2RC2? Christian, Hm. No I didn't change anything in the WSDL file since i don't know = where to change from "document" to "wrapped" in the WSDL file. This relates to my question below where i didn't know where to = change to wrapped. >>Thanks for your hint. Read it up in the documentation and = understand that now. >>How can i specify WRAPPED style parameters? Couldnt find any info = in there except hacking the deploy.wsdd after the wsdl2java. Cheers Thomas ----- Original Message -----=20 From: Faucher, Christian=20 To: axis-user@ws.apache.org=20 Sent: Tuesday, February 22, 2005 18:30 Subject: RE : Is this a serious bug in string parameter passing to = AXIS 1.2RC2? Thomas, iich.. Sorry for the silly question, but I guess you regenarted = your clietn stubs, from your new WSDL? Otherwise, this one beats me. Sorry. Christian -----Message d'origine----- De : thomas willomitzer [mailto:willo@test.at]=20 Envoy=E9 : mardi, f=E9vrier 22, 2005 13:25 =C0 : axis-user@ws.apache.org Objet : Re: Is this a serious bug in string parameter passing to = AXIS 1.2RC2? Christian, thanks again. Changed the style to WRAPPED in the .wsdd file = (the one generated from wsdl2java as below) and am now getting an error = like: (I'm attaching my wsdd file as well below) Do i have to change anything else to make it work again? Sorry = for the huge amount of question's but i think i don't understand the = behavior that well. ------------------- BEGIN ERROR ------------- No such operation 'arg1' AxisFault faultCode: {http://xml.apache.org/axis/}Client faultSubcode:=20 faultString: No such operation 'arg1' faultActor:=20 faultNode:=20 faultDetail:=20 {http://xml.apache.org/axis/}hostname:willo No such operation 'arg1' at = org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.jav= a:221) at = org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java= :128) at = org.apache.axis.encoding.DeserializationContext.endElement(Deserializatio= nContext.java:1083) at = org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1712) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at = org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at org.apache.crimson.parser.Parser2.content(Parser2.java:1963) at = org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691) at = org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667) at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) at = org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at = org.apache.axis.encoding.DeserializationContext.parse(DeserializationCont= ext.java:226) at = org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645) at org.apache.axis.Message.getSOAPEnvelope(Message.java:424) at = org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstand= Checker.java:62) at = org.apache.axis.client.AxisClient.invoke(AxisClient.java:173) at org.apache.axis.client.Call.invokeEngine(Call.java:2719) at org.apache.axis.client.Call.invoke(Call.java:2702) at org.apache.axis.client.Call.invoke(Call.java:2378) at org.apache.axis.client.Call.invoke(Call.java:2301) at org.apache.axis.client.Call.invoke(Call.java:1758) at = com.company.www.PortTypeBindingStub.testOperation(PortTypeBindingStub.jav= a:104) at = com.company.www.ServicePortTestCase.test1ServicePortTestOperation(Service= PortTestCase.java:39) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at = sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java= :39) at = sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI= mpl.java:25) at = com.intellij.rt.execution.junit2.JUnitStarter.main(JUnitStarter.java:31) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at = sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java= :39) at = sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI= mpl.java:25) at = com.intellij.rt.execution.application.AppMain.main(AppMain.java:78) ------------------- END ERROR ------------- ------------ BEGIN WSDD --------------- ------------ END WSDD --------------- ----- Original Message -----=20 From: Faucher, Christian=20 To: axis-user@ws.apache.org=20 Sent: Tuesday, February 22, 2005 18:02 Subject: RE : Is this a serious bug in string parameter = passing to AXIS 1.2RC2? You can specify the style=3D"WRAPPED" attribute in the = ..., in the WSDD. Remove the = provider=3D"java:RPC" though! Or you can generate your own WSDL using java2wsdl, using a cli = arg, which I dont remember the name. Type "/?", shoudl give you more = info Christian Faucher -----Message d'origine----- De : thomas willomitzer [mailto:willo@test.at]=20 Envoy=E9 : mardi, f=E9vrier 22, 2005 12:56 =C0 : axis-user@ws.apache.org Objet : Re: Is this a serious bug in string parameter passing = to AXIS 1.2RC2? Christian, Thanks for your hint. Read it up in the documentation and = understand that now. How can i specify WRAPPED style parameters? Couldnt find any = info in there except hacking the deploy.wsdd after the wsdl2java. Thanks a lot Thomas ----- Original Message -----=20 From: Faucher, Christian=20 To: axis-user@ws.apache.org=20 Sent: Tuesday, February 22, 2005 17:39 Subject: RE : Is this a serious bug in string parameter = passing to AXIS 1.2RC2? Hi, You WSDL defines a "document" style WS. Documen-style WS = are made to receive a bean, with all the parameters in it e.g. public class MyParamsBean { String str1; String str2; } and=20 void yourMethod(MyParamsBean params); If you wish to keep the parameters separated in your = method, you should use the WRAPPED style: void yourMethod(String str1, String str2); Hope it helps! Christian Faucher -----Message d'origine----- De : thomas willomitzer [mailto:willo@test.at] Envoy=E9 : mardi, f=E9vrier 22, 2005 12:35 =C0 : axis-user@ws.apache.org Objet : Is this a serious bug in string parameter passing = to AXIS 1.2RC2? Hello! I'm having problems with string parameters in AXIS 1.2RC2. I created a simple WSDL to test parameter passing and AXIS = doesn't process the parameters correctly on the Server side. Only the = first parameter gets set to the value in the request, the 2nd and 3rd = are set to null in the service method attached below. I traced the call with tcpmon and everything looks alright = (well...as far as I can tell) I assume I'm doing something wrong as this = basic behavior is probably working correctly. I am trying to get this = work for two days now and don't have any more ideas how to fix that. Please have a look at my WSDL and the TCPMon Trace. I generated the client and server with wsdl2java -s -t = file.wsdl Thanks a lot Thomas ------------------ START Service Method --------------- /** * PortTypeBindingImpl.java * * This file was auto-generated from WSDL * by the Apache Axis 1.2RC2 Nov 16, 2004 (12:19:44 EST) = WSDL2Java emitter. */ package com.company.www; public class PortTypeBindingImpl implements = com.company.www.PortType{ public void testOperation(java.lang.String arg1, = java.lang.String arg2, java.lang.String arg3) throws = java.rmi.RemoteException { System.out.println("Hello"); } } ------------------ END Service Method --------------- ------------------ START WSDL ---------------- = ------------------ END WSDL ---------------- ------------------ START SOAP REQUEST ---------------- POST /axis/services/ServicePort HTTP/1.0 Content-Type: text/xml; charset=3Dutf-8 Accept: application/soap+xml, application/dime, = multipart/related, text/* User-Agent: Axis/1.2RC2 Host: 127.0.0.1:8080 Cache-Control: no-cache Pragma: no-cache SOAPAction: = "capeconnect:ServicePort:PortType#testOperation" Content-Length: 307 value1 value2 value3 ------------------ END SOAP REQUEST ---------------- ------------------ START SOAP REPLY ---------------- HTTP/1.0 200 OK Server: Resin/3.0.8 Content-Type: text/xml; charset=3Dutf-8 Date: Tue, 22 Feb 2005 17:28:47 GMT ------------------ END SOAP REPLY---------------- ------------------------------------------------------------------ "Ce message est confidentiel, =E0 l'usage exclusif du = destinataire ci-dessus et son contenu ne repr=E9sente en aucun cas un = engagement de la part de AXA, sauf en cas de stipulation expresse et par = =E9crit de la part de AXA. Toute publication, utilisation ou diffusion, = m=EAme partielle, doit =EAtre autoris=E9e pr=E9alablement. Si vous = n'=EAtes pas destinataire de ce message, merci d'en avertir = imm=E9diatement l'exp=E9diteur." "This e-mail message is confidential, for the exclusive = use of the addressee and its contents shall not constitute a commitment = by AXA, except as otherwise specifically provided in writing by AXA. Any = unauthorized disclosure, use or dissemination, either whole or partial, = is prohibited. If you are not the intended recipient of the message, = please notify the sender immediately." ------=_NextPart_000_0097_01C518DC.BE5BDBD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
Yup, same issue here Christian.  = The java2wsdl=20 generates a different WSDL than Axis does when it auto-generates the=20 WSDl.
----- Original Message -----
From:=20 Faucher, = Christian
Sent: Tuesday, February 22, = 2005 12:42=20 PM
Subject: RE : Is this a serious = bug in=20 string parameter passing to AXIS 1.2RC2?

Thomas,
 
I=20 see.
 
I=20 generated my WSDL using java2wsdl, specifying the proper CLI argument = for=20 WRAPPED.   I do not use the auto-generated one, which = is=20 sligthly different from the one generated with java2wsdl.   = I=20 couldn't get the auto-generated (?wsdl) to bet ".net friendly", but my = java2wsdl one is.
 
Christian Faucher
-----Message d'origine-----
De : thomas = willomitzer=20 [mailto:willo@test.at]
Envoy=E9 : mardi, f=E9vrier = 22, 2005=20 13:38
=C0 : = axis-user@ws.apache.org
Objet : Re:=20 Is this a serious bug in string parameter passing to AXIS=20 1.2RC2?

Christian,
 
Hm. No I didn't change anything in = the WSDL=20 file since i don't know where to change from "document" to "wrapped" = in the=20 WSDL file.
This relates to my question below = where i=20 didn't know where to change to wrapped.
 
>>Thanks for your hint. Read = it up in the=20 documentation and understand that now.
>>How can i specify WRAPPED = style=20 parameters? Couldnt find any info in there except hacking the = deploy.wsdd=20 after the wsdl2java.
 
Cheers
Thomas
----- Original Message ----- =
From:=20 Faucher, = Christian=20
Sent: Tuesday, February 22, = 2005=20 18:30
Subject: RE : Is this a = serious bug=20 in string parameter passing to AXIS 1.2RC2?

Thomas,
 
iich..   Sorry for the silly question, but I = guess you=20 regenarted your clietn stubs, from your new = WSDL?
 
Otherwise, this one beats me.  = Sorry.
 
Christian
-----Message = d'origine-----
De :=20 thomas willomitzer [mailto:willo@test.at] =
Envoy=E9 :=20 mardi, f=E9vrier 22, 2005 13:25
=C0 : axis-user@ws.apache.org
Objet :=20 Re: Is this a serious bug in string parameter passing to AXIS=20 1.2RC2?

Christian,
 
thanks again. Changed the style = to WRAPPED=20 in the .wsdd file (the one generated from wsdl2java as below) = and am now=20 getting an error like:
(I'm attaching my wsdd file as = well=20 below)
Do i have to change anything = else to make=20 it work again? Sorry for the huge amount of question's but i = think i=20 don't understand the behavior that well.
 
------------------- BEGIN ERROR = -------------
No such operation=20 'arg1'
AxisFault
 faultCode:=20 {http://xml.apache.org/axis/}Client
 faultSubcode:=20
 faultString: No such operation = 'arg1'
 faultActor:=20
 faultNode:
 faultDetail:=20 =
 {http://xml.apache.org/axis/}hostname:willo
 
No such operation = 'arg1'
 at=20 = org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.jav= a:221)
 at=20 = org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java= :128)
 at=20 = org.apache.axis.encoding.DeserializationContext.endElement(Deserializatio= nContext.java:1083)
 at=20 = org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1712)
&nbs= p;at=20 = org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
 at = = org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
&nbs= p;at=20 = org.apache.crimson.parser.Parser2.content(Parser2.java:1963)
 at = = org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
&nbs= p;at=20 = org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
&nbs= p;at=20 = org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
 at=20 = org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
=  at=20 = javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
 at=20 = org.apache.axis.encoding.DeserializationContext.parse(DeserializationCont= ext.java:226)
 at=20 = org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645)
 at= =20 = org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
 at=20 = org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstand= Checker.java:62)
 at=20 = org.apache.axis.client.AxisClient.invoke(AxisClient.java:173)
 at= =20 = org.apache.axis.client.Call.invokeEngine(Call.java:2719)
 at=20 org.apache.axis.client.Call.invoke(Call.java:2702)
 at=20 org.apache.axis.client.Call.invoke(Call.java:2378)
 at=20 org.apache.axis.client.Call.invoke(Call.java:2301)
 at=20 org.apache.axis.client.Call.invoke(Call.java:1758)
 at=20 = com.company.www.PortTypeBindingStub.testOperation(PortTypeBindingStub.jav= a:104)
 at=20 = com.company.www.ServicePortTestCase.test1ServicePortTestOperation(Service= PortTestCase.java:39)
 at=20 sun.reflect.NativeMethodAccessorImpl.invoke0(Native = Method)
 at=20 = sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java= :39)
 at=20 = sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI= mpl.java:25)
 at=20 = com.intellij.rt.execution.junit2.JUnitStarter.main(JUnitStarter.java:31)<= BR> at=20 sun.reflect.NativeMethodAccessorImpl.invoke0(Native = Method)
 at=20 = sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java= :39)
 at=20 = sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI= mpl.java:25)
 at=20 = com.intellij.rt.execution.application.AppMain.main(AppMain.java:78)
------------------- END ERROR=20 -------------
 
------------ BEGIN WSDD=20 ---------------
<deployment
   =20 xmlns=3D"http://xml.apache.org/axis/wsdd= /"
   =20 xmlns:java=3D"http://xml.apache= .org/axis/wsdd/providers/java">
 
  <!-- Services from = ServicePort=20 WSDL service -->
 
  <service = name=3D"ServicePort"=20 style=3D"WRAPPED" = use=3D"literal">
     =20 <parameter name=3D"wsdlTargetNamespace" value=3D"http://www.company.com"/>
&nb= sp;    =20 <parameter name=3D"wsdlServiceElement"=20 value=3D"ServicePort"/>
      = <parameter=20 name=3D"wsdlServicePort"=20 value=3D"ServicePort"/>
      = <parameter=20 name=3D"className"=20 = value=3D"com.company.www.PortTypeBindingImpl"/>
   &= nbsp; =20 <parameter name=3D"wsdlPortType"=20 value=3D"PortType"/>
      = <operation=20 name=3D"testOperation" qname=3D"testOperation"=20 soapAction=3D"capeconnect:ServicePort:PortType#testOperation"=20 >
        <parameter = qname=3D"arg1" type=3D"tns:string" xmlns:tns=3D"http://www.w3.org/2001/XMLSch= ema"/>
       =20 <parameter qname=3D"arg2" type=3D"tns:string" xmlns:tns=3D"http://www.w3.org/2001/XMLSch= ema"/>
       =20 <parameter qname=3D"arg3" type=3D"tns:string" xmlns:tns=3D"http://www.w3.org/2001/XMLSch= ema"/>
     =20 </operation>
      = <parameter=20 name=3D"allowedMethods" = value=3D"testOperation"/>
 
 =20 </service>
</deployment>
------------ END WSDD=20 ---------------
----- Original Message ----- =
From:=20 Faucher, = Christian=20
To: axis-user@ws.apache.org=20
Sent: Tuesday, February = 22, 2005=20 18:02
Subject: RE : Is this a = serious=20 bug in string parameter passing to AXIS 1.2RC2?

You can specify the style=3D"WRAPPED" attribute in = the=20 <service ...style=3D"WRAPPED">...</service>, in = the=20 WSDD.  Remove the provider=3D"java:RPC"=20 though!
 
Or you can generate your own WSDL using java2wsdl, = using a cli=20 arg, which I dont remember the name.  Type "/?", shoudl = give you=20 more info
 
Christian Faucher
 
-----Message=20 d'origine-----
De : thomas willomitzer=20 [mailto:willo@test.at]
Envoy=E9 : mardi, = f=E9vrier 22,=20 2005 12:56
=C0 :=20 axis-user@ws.apache.org
Objet : Re: Is this a = serious=20 bug in string parameter passing to AXIS = 1.2RC2?

Christian,
 
Thanks for your hint. Read = it up in the=20 documentation and understand that now.
How can i specify WRAPPED = style=20 parameters? Couldnt find any info in there except hacking = the=20 deploy.wsdd after the wsdl2java.
 
Thanks a lot
Thomas
----- Original Message = -----
From:=20 Faucher,=20 Christian
To: axis-user@ws.apache.org=20
Sent: Tuesday, = February 22,=20 2005 17:39
Subject: RE : Is = this a=20 serious bug in string parameter passing to AXIS = 1.2RC2?

Hi,
 
You WSDL = defines a=20 "document" style WS.  Documen-style WS are made to = receive a=20 bean, with all the parameters in it e.g.
 
public = class=20 MyParamsBean {
    String str1;
    String str2;
}
and =
    void=20 yourMethod(MyParamsBean params);
 
If you = wish to keep the=20 parameters separated in your method, you should use the = WRAPPED=20 style:
    void=20 yourMethod(String str1, String str2);
 
Hope it=20 helps!

Christian=20 Faucher


-----Message d'origine-----
De : = thomas=20 willomitzer [mailto:willo@test.at]
Envoy=E9 :=20 mardi, f=E9vrier 22, 2005 12:35
=C0 :=20 axis-user@ws.apache.org
Objet : Is this a serious bug = in string=20 parameter passing to AXIS = 1.2RC2?


Hello!

I'm=20 having problems with string parameters in AXIS = 1.2RC2.
I=20 created a simple WSDL to test parameter passing and AXIS = doesn't=20 process the parameters correctly on the Server side. Only = the=20 first parameter gets set to the value in the request, the = 2nd and=20 3rd are set to null in the service method attached = below.

I=20 traced the call with tcpmon and everything looks alright=20 (well...as far as I can tell) I assume I'm doing something = wrong=20 as this basic behavior is probably working correctly. I am = trying=20 to get this work for two days now and don't have any more = ideas=20 how to fix that.

Please have a look at my WSDL and = the=20 TCPMon Trace.
I generated the client and server with = wsdl2java=20 -s -t file.wsdl

Thanks a=20 lot
Thomas

------------------ START Service = Method=20 ---------------
/**
 *=20 PortTypeBindingImpl.java
 *
 * This file = was=20 auto-generated from WSDL
 * by the Apache Axis = 1.2RC2 Nov=20 16, 2004 (12:19:44 EST) WSDL2Java emitter.  = */

package=20 com.company.www;

public class PortTypeBindingImpl=20 implements com.company.www.PortType{
    = public=20 void testOperation(java.lang.String arg1, java.lang.String = arg2,=20 java.lang.String arg3) throws java.rmi.RemoteException=20 {
       =20 System.out.println("Hello");
   =20 }

}
------------------ END Service Method=20 ---------------


------------------ START WSDL=20 ----------------
<?xml version=3D"1.0"=20 = encoding=3D"UTF-8"?>
<wsdl:definitions
   =20 name=3D"ParamTest"
    = targetNamespace=3D"http://www.company.com"
 &nbs= p; =20 xmlns:comp=3D"http://www.company.com"
 &nbs= p; =20 xmlns:soap=3D"http://schemas.xmlsoap.org= /wsdl/soap/"
   =20 xmlns:tns=3D"http://www.company.com"
 &nbs= p; =20 xmlns:wsdl=3D"http://schemas.xmlsoap.org/wsdl= /"
   =20 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchem= a">
   =20 <wsdl:types> = </wsdl:types>
   =20 <wsdl:message = name=3D"testOperationResponse">  =20 </wsdl:message>
    = <wsdl:message=20 = name=3D"testOperationRequest">
      =  =20 <wsdl:part name=3D"arg1"=20 = type=3D"xsd:string"/>
       =20 <wsdl:part name=3D"arg2"=20 = type=3D"xsd:string"/>
       =20 <wsdl:part name=3D"arg3"=20 type=3D"xsd:string"/>
   =20 </wsdl:message>
    = <wsdl:portType=20 = name=3D"PortType">
       =20 <wsdl:operation=20 = name=3D"testOperation">
       &= nbsp;   =20 <wsdl:input=20 = message=3D"tns:testOperationRequest"/>
    &nbs= p;      =20 <wsdl:output=20 = message=3D"tns:testOperationResponse"/>
    &nb= sp;  =20 </wsdl:operation>
   =20 </wsdl:portType>
    = <wsdl:binding=20 name=3D"PortTypeBinding"=20 = type=3D"tns:PortType">
       =20 <soap:binding style=3D"document" transport=3D"http://schemas.xmlsoap.org/= soap/http"/>
       =20 <wsdl:operation=20 = name=3D"testOperation">
       &= nbsp;   =20 = <soap:operation
        &nb= sp;      =20 = soapAction=3D"capeconnect:ServicePort:PortType#testOperation"
 &n= bsp;           &nb= sp; =20 = style=3D"document"/>
       &nbs= p;   =20 = <wsdl:input>
        &nb= sp;      =20 <soap:body parts=3D"arg3 arg1 arg2"=20 = use=3D"literal"/>
        &= nbsp;  =20 = </wsdl:input>
        &n= bsp;  =20 = <wsdl:output>
        &n= bsp;      =20 <soap:body=20 = use=3D"literal"/>
        &= nbsp;  =20 = </wsdl:output>
       =20 </wsdl:operation>
   =20 </wsdl:binding>
    = <wsdl:service=20 = name=3D"ServicePort">
       =20 <wsdl:port binding=3D"tns:PortTypeBinding"=20 = name=3D"ServicePort">
       &nb= sp;   =20 <soap:address location=3D"http://willo/axis/service= s/ServicePort"/>
       =20 </wsdl:port>
   =20 = </wsdl:service>
</wsdl:definitions>
------------------ = END WSDL ----------------


------------------ = START SOAP=20 REQUEST ----------------
POST = /axis/services/ServicePort=20 HTTP/1.0
Content-Type: text/xml; = charset=3Dutf-8
Accept:=20 application/soap+xml, application/dime, multipart/related, = text/*
User-Agent: Axis/1.2RC2
Host:=20 127.0.0.1:8080
Cache-Control: no-cache
Pragma:=20 no-cache
SOAPAction:=20 = "capeconnect:ServicePort:PortType#testOperation"
Content-Length:=20 307

<soapenv:Envelope xmlns:soapenv=3D"http://schemas.xmlsoap= .org/soap/envelope/"
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchem= a"
xmlns:xsi=3D"http://www.w3.org/2001= /XMLSchema-instance">
  =20 <soapenv:Body>
      = <arg1=20 = xmlns=3D"">value1</arg1>
     =20 <arg2=20 = xmlns=3D"">value2</arg2>
     =20 <arg3 xmlns=3D"">value3</arg3>
   = = </soapenv:Body></soapenv:Envelope>
------------------=20 END SOAP REQUEST = ----------------

------------------ START=20 SOAP REPLY ----------------
HTTP/1.0 200 OK
Server:=20 Resin/3.0.8
Content-Type: text/xml; = charset=3Dutf-8
Date: Tue,=20 22 Feb 2005 17:28:47 GMT

<soapenv:Envelope=20 xmlns:soapenv=3D"http://schemas.xmlsoap= .org/soap/envelope/"
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchem= a"
xmlns:xsi=3D"http://www.w3.org/2001= /XMLSchema-instance">
  =20 <soapenv:Body>
     =20 <arg1Response xmlns=3D""/>
  =20 = </soapenv:Body></soapenv:Envelope>
------------------=20 END SOAP = REPLY----------------


"Ce=20 message est confidentiel, =E0 l'usage exclusif du = destinataire=20 ci-dessus et son contenu ne repr=E9sente en aucun cas un = engagement=20 de la part de AXA, sauf en cas de stipulation expresse et = par=20 =E9crit de la part de AXA. Toute publication, utilisation = ou=20 diffusion, m=EAme partielle, doit =EAtre autoris=E9e = pr=E9alablement. Si=20 vous n'=EAtes pas destinataire de ce message, merci d'en = avertir=20 imm=E9diatement l'exp=E9diteur."

"This e-mail = message is=20 confidential, for the exclusive use of the addressee and = its=20 contents shall not constitute a commitment by AXA, except = as=20 otherwise specifically provided in writing by AXA. Any=20 unauthorized disclosure, use or dissemination, either = whole or=20 partial, is prohibited. If you are not the intended = recipient of=20 the message, please notify the sender immediately."=20
------=_NextPart_000_0097_01C518DC.BE5BDBD0--