Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 7603 invoked from network); 28 Jul 2006 20:51:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Jul 2006 20:51:29 -0000 Received: (qmail 44722 invoked by uid 500); 28 Jul 2006 20:51:21 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 44704 invoked by uid 500); 28 Jul 2006 20:51:21 -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: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 44693 invoked by uid 99); 28 Jul 2006 20:51:20 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Jul 2006 13:51:20 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of atmanes@gmail.com designates 64.233.182.185 as permitted sender) Received: from [64.233.182.185] (HELO nf-out-0910.google.com) (64.233.182.185) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Jul 2006 13:51:20 -0700 Received: by nf-out-0910.google.com with SMTP id x29so203908nfb for ; Fri, 28 Jul 2006 13:50:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BZt1BDaeY3Q9k30QiNKFoCM7lD0Ai0YSu7/OE1kkXdKBdrW+qh05CLfDRp0Lgk55NNwF+Ioy2vOSXHGOkmRHmYx9v2wzwmZC2h3Co9LLtWQEKcdnZfGdHnMCdEur/daoLTgOPRLDGCsJWd+AtbrGyFwSl6G6MeG5fPmaNPej4Tc= Received: by 10.78.140.17 with SMTP id n17mr988898hud; Fri, 28 Jul 2006 13:50:58 -0700 (PDT) Received: by 10.78.71.3 with HTTP; Fri, 28 Jul 2006 13:50:58 -0700 (PDT) Message-ID: Date: Fri, 28 Jul 2006 16:50:58 -0400 From: "Anne Thomas Manes" To: axis-user@ws.apache.org Subject: Re: [Axis2 1.0] authoring WSDL In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N As I said, for unwrapped document style, you don't need to use a void type. Instead, you should specify a message with no parts: You should use WS-Addressing and the Action parameter to indicate the method you want to invoke. For a oneway message, you define an operation with an input message, but no output message, e.g., Anne On 7/28/06, Nirmit Desai wrote: > Hi Anne, > > thanks a lot for a detailed response. > > I am doing document/literal services in Axis2 ( I am assuming document and > unwrapped are identical). I start by defining a WSDL, doing WSDL2Java, > flesh out business logic and then deploy. But, > > > > creates a VoidType.java during codeGen for me in ADB as posted here: > http://marc.theaimsgroup.com/?l=axis-user&m=115404237314689&w=2 > > For fire and forget, when you say there is no return message, you mean the > operation output does not have to be specified? > > Thanks, > > -Nirmit > > > > > > "Anne Thomas > Manes" > m> axis-user@ws.apache.org > cc > 07/28/2006 11:26 > AM Subject > Re: [Axis2 1.0] authoring WSDL > > Please respond to > axis-user@ws.apac > he.org > > > > > > > I've never seen such a document. I do recommend using a WSDL authoring > tool, such as xmlspy, Sonic Stylus, or . > > Guidelines for operations with no argument (input or output) will be > different depending on the message style, programming model, and > message exchange pattern (MEP) you're using. > > Typically, I define a void type like this: > > > > > > You could also define it like this: > > > > but this definition doesn't work with the "wrapped" style (which > requires the ). > > For unwrapped document style, you can define an input message with no > argument like this: > > > > This will send an empty message, e.g., . You just need to > make sure that the receiving SOAP engine knows how to dispatch the > request, because the input message has no signature. (Typically used > with the Message receiver in Axis 1. Axis2 lets you dispatch based on > the Action paramater.) > > For wrapped document style, you must define an element which has the > same name as the operation, whose type is void: > > > > And define the message as: > > > > > > For rpc style, you define a message with no parts: > > > > As for the return message... > > For a oneway MEP (fire and forget), there is no return message. > > For a request/response MEP: > > For unwrapped document or rpc style, you define a message with no parts: > > > > For wrapped document style, you must define a response element whose > type is void: > > > > And define the message as: > > > > > > Hope this helps. > > Anne > > On 7/28/06, Nirmit Desai wrote: > > > > Hi all, > > > > I was wondering if anyone has a pointer a good comprehensive WSDL > authoring > > guidelines. > > > > For now, I am wondering how to write WASDL for an operation that doesn't > > take any arguments. Or for an operation that returns void. I want these > to > > be asynchronous. I would like to call the void returning operation with > > fireAndForget(). > > > > Thanks, > > > > -Nirmit > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > > For additional commands, e-mail: axis-user-help@ws.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-user-help@ws.apache.org