You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by danclemson <da...@gmail.com> on 2008/05/06 20:51:52 UTC

Axis2 web service client compatibility

Hi,

I am new to both web service and axis2, and I have a few questions after
reading the manual and examples.
 
There are diffenernt ways to build web service using axis2. for example
using pojo, axiom, or databinding. My question is if I choose to build my
web service using axiom, does this forces the client to rely on axiom as
well? 

Another question is that if the I choose to use rampart for user
authentication, does this require the client to use rampart as well?

thanks /dan
-- 
View this message in context: http://www.nabble.com/Axis2-web-service-client-compatibility-tp17089892p17089892.html
Sent from the Axis - User mailing list archive at Nabble.com.


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


Re: Axis2 web service client compatibility

Posted by Amila Suriarachchi <am...@gmail.com>.
On Wed, May 7, 2008 at 6:55 AM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

> danclemson wrote:
>
>> Hi,
>>
>> I am new to both web service and axis2, and I have a few questions after
>> reading the manual and examples.
>>  There are diffenernt ways to build web service using axis2. for example
>> using pojo, axiom, or databinding. My question is if I choose to build my
>> web service using axiom, does this forces the client to rely on axiom as
>> well?
>
> Nope the idea of the web services is to communicate using the soap so that
it can be independent of the implementation.
Here you have to keep in mind that your service interface (request and
response message formats) should be declared in the wsdl. Basically what
ever the client get to know about the expected request format using the
wsdl. Therefore if you write a service with Axiom the correct contract may
not be displayed in the
wsdl. So that may cause some problems.

Therefore it is better to use the wsdl2java tool (contract first is the
recommended way) or POJO to increase the interoperability.

thanks,
Amila.

>
>>
> Nop. your client can be .NET and what goes over the wire is XML, that is
> the whole point of Web services.
>
>  Another question is that if the I choose to use rampart for user
>> authentication, does this require the client to use rampart as well?
>>
>>
>
> Nop, but the client needs to send user auth headders somehow.
>
> Samisa...
>
>  thanks /dan
>>
>>
>
>
> --
> Samisa Abeysinghe
>
> http://people.apache.org/~samisa/ <http://people.apache.org/%7Esamisa/>
>
>
>
> ---------------------------------------------------------------------
> 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.

Re: Axis2 web service client compatibility

Posted by Samisa Abeysinghe <sa...@gmail.com>.
danclemson wrote:
> Hi,
>
> I am new to both web service and axis2, and I have a few questions after
> reading the manual and examples.
>  
> There are diffenernt ways to build web service using axis2. for example
> using pojo, axiom, or databinding. My question is if I choose to build my
> web service using axiom, does this forces the client to rely on axiom as
> well? 
>   

Nop. your client can be .NET and what goes over the wire is XML, that is 
the whole point of Web services.

> Another question is that if the I choose to use rampart for user
> authentication, does this require the client to use rampart as well?
>   

Nop, but the client needs to send user auth headders somehow.

Samisa...

> thanks /dan
>   


-- 
Samisa Abeysinghe

http://people.apache.org/~samisa/


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