WS-Transfer protocol using AXIS2

[Fabien Couble <fa...@capgemini.com>]

Hi everybody,

I'd like advices concerning a project I have to do using Apache AXIS2.
Actually, I have to implement the WS-Transfer protocol using Apache AXIS2. I spent time to understand how AXIS2 works and I have some questions. Maybe you could answer to them:

    First of all, implementing the WS-Transfer protocol consists in formatting messages in a special format and understanting these messages in order to send appropriate responses. 
After studying AXIS2, I have noticed its extensibility by the addition of modules. These modules can touch the message meaning the header and the body. That is why, I was wondering if it is better to use this concept or declare everything in the WSDL file describing the service? In fact, I also analysed the wsdl language and I have noticed that a SOAP binding exists which permits to specify the message format.

That is why, I don't really know which method is preferable and more convenient?

Moerover, if you can advise me some good documentations on the WSDL language, I would be glad  to take them...

Any comment is welcome!

Cheers 
Fabien



This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.

Re: WS-Transfer protocol using AXIS2

[David Illsley <da...@uk.ibm.com>]

Hi Fabien,
I've had a quick read of the WS-Transfer spec and while I think you could 
go many directions with the implementation, the fastest was is probably 
just to implement as a service.

This is because the spec defines a number of operations get/put/delete and 
create which are not logically associated with any other services. 
Additionally, though the spec mentions headers, these are just 
WS-Addressing headers which you can get/set using the standard Axis2 
addressing apis and you don't need to worry about accessing the headers.

Modules are a good fit when you have to add your own handlers to process 
headers or add new services/operations to existing services but those 
don't seem to be required for implementing WS-Transfer.

WSDL can be a bit ugly but is pretty logical and there is a good start 
with the wsdl publiushed at [1]. My suggestion is to google for a WSDL 
tutorial and look at the binding/port/service bit to complete the WSDL 
already provided (should be pretty straightforward).

David

[1] http://schemas.xmlsoap.org/ws/2004/09/transfer/transfer.wsdl

"Fabien Couble" <fa...@capgemini.com> wrote on 07/24/2006 
09:18:32 AM:

> Hi everybody,
> 
> I'd like advices concerning a project I have to do using Apache AXIS2.
> Actually, I have to implement the WS-Transfer protocol using Apache 
> AXIS2. I spent time to understand how AXIS2 works and I have some 
> questions. Maybe you could answer to them:
> 
>     First of all, implementing the WS-Transfer protocol consists in 
> formatting messages in a special format and understanting these 
> messages in order to send appropriate responses. 
> After studying AXIS2, I have noticed its extensibility by the 
> addition of modules. These modules can touch the message meaning the
> header and the body. That is why, I was wondering if it is better to
> use this concept or declare everything in the WSDL file describing 
> the service? In fact, I also analysed the wsdl language and I have 
> noticed that a SOAP binding exists which permits to specify the 
> message format.
> 
> That is why, I don't really know which method is preferable and more
> convenient?
> 
> Moerover, if you can advise me some good documentations on the WSDL 
> language, I would be glad  to take them...
> 
> Any comment is welcome!
> 
> Cheers 
> Fabien
> 
> 
> 
> This message contains information that may be privileged or 
> confidential and is the property of the Capgemini Group. It is 
> intended only for the person to whom it is addressed. If you are not
> the intended recipient, you are not authorized to read, print, 
> retain, copy, disseminate, distribute, or use this message or any 
> part thereof. If you receive this message in error, please notify 
> the sender immediately and delete all copies of this message.


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