[AXIS2] WSDL generation

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

Hi all,

I'm trying to deploy a service WS-Transfer. I have created a wsdl file to describe this service. Then, I have generated my stub and skeleton. The generation seems allright but actually it is not the generation I expected.
Actually, I have declared messages with parameters but the generation produces methods without any parameters. 
I think there is a problem in my wsdl file.
Actually, I want to create a service with 3 operations: GET, PUT and CREATE. 
I want that the method GET has an input messages with an empty body and a response with a body containing xml data without a predefined structure.
And so on...

I have created the enclodes WSDL file... If you can have a look to it, it could be great
Any comment is welcome


THx - 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: [AXIS2] WSDL generation

[Sanjiva Weerawarana <sa...@opensource.lk>]

On Tue, 2006-07-25 at 14:03 -0400, Anne Thomas Manes wrote:
> Note that WS-Transfer relies on WS-Addressing to specify the target
> resource and the operation to be performed. Therefore, it requires
> that you use a SOAP engine that can route and dispatch requests based
> on WS-Addressing. Axis 1 cannot do this. I'm not sure if Axis2 is
> capable of doing this. 

It absolutely is! :)

Sanjiva.



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

Re: [AXIS2] WSDL generation

[Anne Thomas Manes <at...@gmail.com>]

Note that WS-Transfer relies on WS-Addressing to specify the target resource
and the operation to be performed. Therefore, it requires that you use a
SOAP engine that can route and dispatch requests based on WS-Addressing.
Axis 1 cannot do this. I'm not sure if Axis2 is capable of doing this.

(Note that WS-Transfer is not WS-I compliant because of its dependency on
WS-Addressing.)

Anne

On 7/25/06, Fabien Couble <fa...@capgemini.com> wrote:
>
>  Hi all,
>
> I'm trying to deploy a service WS-Transfer. I have created a wsdl file to
> describe this service. Then, I have generated my stub and skeleton. The
> generation seems allright but actually it is not the generation I expected.
> Actually, I have declared messages with parameters but the generation
> produces methods without any parameters.
> I think there is a problem in my wsdl file.
> Actually, I want to create a service with 3 operations: GET, PUT and
> CREATE.
> I want that the method GET has an input messages with an empty body and a
> response with a body containing xml data without a predefined structure.
> And so on...
>
> I have created the enclodes WSDL file... If you can have a look to it, it
> could be great
> Any comment is welcome
>
>
> THx - 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
>
>
>