Hi,
Sorry not being able to reply earlier.
Assume my wsdl has following service bindings,
...
<service name="Foo">
<port name="a">...</port>
</service>
<service name="Bar">
<port name="b">...</port>
</service>
...
Now according to the prior discussion, if use wsdl2java, It'll create
FooAStub and FooBStub right?
Now if we have a single service binding [assume service binding name is Foo
with port binding name is A] or if we use -sn and -pn
That would generate FooAStub.
If we look at Axis2 1.1 till now, if we use the above for single service
binding it would generate only FooStub.
With your proposal wouldn't this break the backward compatibility. Is it
good for Systems that's already using Axis2 1.1 and want to change to Axis2
1.2 ?
Thank you
Saminda
On 3/14/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
I implemented the multi service and multi port support in the following
way.
if the user has specified a service and a port (using -sn and -pn) then
the wsdl2java generates the code only for that combination. otherwise it
generates the code for all services and ports.
When Generating code for multiple ports (i.e when user has not specified
any service name or ports)
first it picks a soap binding and generates the code for the bindings with
the same portType as the chosen binding. other ports are ignored.
I could not figure out a method to add multi service support for jibx
binding. So I kept the getAxisService method in codegenConfiguration to
support jibx. Denis can you please look into this?
--
Amila Suriarachchi,
WSO2 Inc.
--
Saminda Abeyruwan
Software Engineer
WSO2 Inc. - www.wso2.org
