Ajith,
Thanks for your quick reply and the
suggestions. I will look forward to try out the wsdl generation features. I
presume it will be closely tied to the data binding piece (or the code
generation thereof).
Please suggest if my understanding is
correct
1. When I create a new service afresh
and if I use the following method for my operation implementation
OMElement operation(OMElement)
I may not get to configure my concrete
soap binding to a great extent apart from say style. Otherwise I will end up implementing
much of SOAP myself.
2. When I create a service
implementation based on some concrete wsdl for the purpose of replacing someone else’s service
implementation, I will most likely use the code generation tool. Hopefully the
tool will create the necessary data binding code and a services.xml file based
on my original concrete wsdl file. So the new service will look exactly same as
the one being replaced.
3. I read somewhere on this mailing list
that axis2 is going to support SOAP encoding in addition to WS-I BP (I assume
both doc/lit and rpc/lit) in the GA version. Is that a correct assumption?
Thanks again for your help and best
wishes to you and the Axis2 team.
Dinesh
From: Ajith
Ranabahu [mailto:[EMAIL PROTECTED]
Sent: Monday, December 26, 2005
9:29 PM
To: [email protected]
Subject: Re: [axis2] WSDL for deployed
service
Hi Dinesh,
I suppose the question is about the WSDL generation in Axis2. By the time we
shipped .93 this support was not complete so we did not advertise it :) (that
is why the documents are missing)
However progress has been made in this area and basic doc/lit WSDL can be
generated right now. We do not have tweaking options yet (like the style and
custom header addition capabilities). So if you would wait a couple of more
weeks (?) you might see a .9x release with WSDL generation capability. And yes,
this WSDL generation will take information from the services.xml too.
However I can suggest an immediate workaround for your case. Since the
Axis Engine has the capability to generate the binding and the service when an
interface WSDL is included, you can do the following and try
1. Handcraft a WSDL for your service - I guess you can do with an interface
WSDL (upto the porttype) but unless there's atleast a dummy binding, the code
generator won't generate a message receiver! (BTW I can recommend capeclears
SOA editor for WSDL editing. It's a good tool)
2. Archive the classes and include the WSDL in the meta-inf directory (please
look into the documentation for this)
3. When you ask for the WSDL (by ?wsdl) you should see a WSDL that can be used
to access the service.
On 12/27/05, Dinesh Shahane <[EMAIL PROTECTED]> wrote:
Dear Axis Developers,
It seems like a basic question but I couldn't find it from the
documentation, your help will be greatly appreciated.
How do you get the concrete wsdl for a service deployed in Axis2?
Moreover I couldn't find any information on configuring style, encoding
or custom soap headers etc. for my service. Is it supposed to be in
services.xml file?
Do I have to manually craft the wsdl by hand for now? I am using the
version 0.93.
Thanks in advance.
Dinesh
--
Ajith Ranabahu
