Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 22198 invoked from network); 25 Apr 2006 22:53:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Apr 2006 22:53:21 -0000 Received: (qmail 64311 invoked by uid 500); 25 Apr 2006 22:53:09 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 64278 invoked by uid 500); 25 Apr 2006 22:53:08 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 64264 invoked by uid 99); 25 Apr 2006 22:53:08 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Apr 2006 15:53:08 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=HTML_MESSAGE,RCVD_IN_SORBS_WEB,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of enjoyjava@gmail.com designates 64.233.184.234 as permitted sender) Received: from [64.233.184.234] (HELO wproxy.gmail.com) (64.233.184.234) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Apr 2006 15:53:07 -0700 Received: by wproxy.gmail.com with SMTP id i27so947956wra for ; Tue, 25 Apr 2006 15:52:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:from:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=CYFctcH7GvKvJ6whDpcenvLcRVBx1btCyQS0Ko0p8Me9W+hFbgBfO7zaobTlAEbbkAGGf+qjgNCzmRHVvADTP2Sk5qIB/th7JdOc0wDiTYvGvP+X1Z1YTzTxKowZpwokKJVFTVvkDI73AKFD9W8akyObZGBxaKYlr0VRyJyY/Z8= Received: by 10.54.97.9 with SMTP id u9mr4541300wrb; Tue, 25 Apr 2006 15:52:47 -0700 (PDT) Received: from RFENGXP ( [32.97.110.142]) by mx.gmail.com with ESMTP id 38sm779307wrl.2006.04.25.15.52.46; Tue, 25 Apr 2006 15:52:46 -0700 (PDT) Message-ID: <000e01c668ba$fce0bb30$fee51a09@RFENGXP> From: "Raymond Feng" To: Subject: [AXIS2] Question: Does WSDL2Java support doc-lit wrapped style? Date: Tue, 25 Apr 2006 15:52:51 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C66880.4EA58210" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C66880.4EA58210 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I understand Axis1.x WSDL2Java honors doc-lit wrapped style and = generates unwrapped java methods. The following is a quote from the Axis = 1.3 reference guide. "W, --noWrapped=20 This turns off the special treatment of what is called "wrapped" = document/literal style operations. By default, WSDL2Java will recognize = the following conditions:=20 a.. If an input message has is a single part.=20 b.. The part is an element.=20 c.. The element has the same name as the operation=20 d.. The element's complex type has no attributes When it sees this, WSDL2Java will 'unwrap' the top level element, and = treat each of the components of the element as arguments to the = operation. This type of WSDL is the default for Microsoft .NET web = services, which wrap up RPC style arguments in this top level schema = element. " When I tried Axis2 WSDL2Java, it seems that it always generate unwrapped = stubs and skeletons. Is this the direction we're heading? BTW, do we have Java2WSDL support in Axis2? Thanks, Raymond ------=_NextPart_000_000B_01C66880.4EA58210 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I understand Axis1.x = WSDL2Java honors doc-lit=20 wrapped style and generates unwrapped java methods. The following is a = quote=20 from the Axis 1.3 reference guide.
 
"W, --noWrapped
This turns off the special treatment of what is called "wrapped"=20 document/literal style operations. By default, WSDL2Java will recognize = the=20 following conditions:=20
  • If an input message has is a single part.=20
  • The part is an element.=20
  • The element has the same name as the operation=20
  • The element's complex type has no attributes
When it = sees this,=20 WSDL2Java will 'unwrap' the top level element, and treat each of the = components=20 of the element as arguments to the operation. This type of WSDL is the = default=20 for Microsoft .NET web services, which wrap up RPC style arguments in = this top=20 level schema element. "
 
 
When I tried Axis2 WSDL2Java, it seems that it always generate = unwrapped=20 stubs and skeletons. Is this the direction we're heading?
 
BTW, do we have Java2WSDL support in Axis2?
 
Thanks,
Raymond
 
------=_NextPart_000_000B_01C66880.4EA58210--