Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (athena.apache.org: domain of amilasuriarachchi@gmail.com
 designates 209.85.198.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=bz9PQ/1yJPr9G2F9Y4RUDwpeytSj3b9exgPApbgmlJQVGtRrQgL7cQPTo9hN5hdWN50oj13jG8KF++rWVLvwyIe74YSjpS0k8HFYcXZ++fjhnnLPI54SO2yKPMa9agYa17rFMN1T00ie/dcvo+nnEjG2U42jtTJ8TSN6y7CrdrI=
Message-ID: <60708f4b0711120210w30979dbaycc7631b0d0014254@mail.gmail.com>
Date: Mon, 12 Nov 2007 15:40:43 +0530
From: "Amila Suriarachchi" <amilasuriarachchi@gmail.com>
To: axis-user@ws.apache.org
Subject: Re: Custom message receivers vs RPCMessageReceiver
In-Reply-To: <47381CB3.40301@cardinis.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <47381CB3.40301@cardinis.com>

hi,

I think this is a confusion lot of people made.

when developing web services there are two mehtods.
1. contract first approach.
      here you start with the wsdl file (contract ) and use the
wsdl2java to generte the code. so it generates a
      custom message receiver for you.
2. code first approach.
       here you start with code and axis2 generates a wsdl for you.
here you must use the RPCMessageReceiver.

when developing a service you have to choose one. and you can not use
RPCMessageReceiver with the generated code.

thanks,
Amila.


On Nov 12, 2007 2:58 PM, Mauro Molinari <mauro.molinari@cardinis.com> wrote:
> Hello all!
> I have a question about message receivers.
>
> Suppose I have a WSDL with just an in & out operation, whose input and
> output parameters eventually are simple types.
>
> Suppose I want to generate the Java code using WSDL2Java, with the
> unwrapping option (-uw).
>
> For the server-side, WSDL2Java creates a specialized message receiver
> for the service. But, as long as I understood it correctly, because of
> the fact that the only operation in the service uses simple types
> (strings, ints, etc.), I should be able to use an RPCMessageReceiver...
> at last, this is what I find in services.xml if I write equivalent code
> and follow the POJO guide in Axis2 documentation...
>
> So, am I correct? Is there any advantage or drawback on using
> RPCMessageReceiver when working with operations with just simple types
> involved instead of the "customized" message receivers generated by
> WSDL2Java?
>
> Thanks in advance.
>
> --
> Mauro Molinari
> Software Developer
> mauro.molinari@cardinis.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org