unsubscribe
-----Original Message-----
From: Ding, Chengmin [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 04, 2001 3:02 PM
To: '[EMAIL PROTECTED]'
Subject: RE: WSDL
IBM WSTK 2.1 has the built-in functionality to convert .class into .wsdl
It can be started using the command line tool: servicewizard.bat
Then you can go through the generated .wsdl and depolyment decription file
to find out the mappings.
HTH.
-Chengmin
-----Original Message-----
From: Daniel Kruler [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 04, 2001 5:51 PM
To: [EMAIL PROTECTED]
Subject: RE: WSDL
That is what I actually need: Java2WSDL generator.
I am confused about binding and service sections of WSDL.
What should I have in <soap:operation soapAction="????"/> of every
operation in BINDING?
What type of encoding should I specify in USE if I am passing primitive
data types?
How does <service name="XYZ"> correspond to deployment descriptor?
What SOAP address should be used in
<port>
<soap:address location="?????"/>
</port> ?
-----Original Message-----
From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 04, 2001 5:34 PM
To: [EMAIL PROTECTED]
Subject: Re: WSDL
You might want to take a look at what the IBM WSTK or WSDE produce
from a WSDL file to see how WSDL maps to the deployment descriptor
and to the skeleton.
The other direction obviously has nothing to do with a deployment
descriptor etc. as its going from a vanilla Java class to a WSDL
file.
Sanjiva.
----- Original Message -----
From: "Daniel Kruler" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 04, 2001 5:31 PM
Subject: RE: WSDL
> I am trying to write WSDL from Java generator.
> I am not very clear on how different parts of WSDL are mapped to
> deployment descriptor and skeleton implementation.
>
>
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 04, 2001 5:27 PM
> To: [EMAIL PROTECTED]
> Subject: Re: WSDL
>
>
> No- methodNamespaceURI attribute of the soap:body binding element
> is what goes in the ID of the deployment descriptor. Apache SOAP
> currently only routes on the qualified name of the method element
> for SOAP RPC.
>
> Sanjiva.
>
> ----- Original Message -----
> From: "Daniel Kruler" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, June 04, 2001 5:18 PM
> Subject: WSDL
>
>
> > In WSDL does targetNamespace and name correspond to ID in deployment
> > descriptor?
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
