On 3/16/07, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:
<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?
You are lucky if it was just Foo & A... Kandula2 wsdl's generated BACoordinatorCompletionParticipantServiceBACoordinatorCompletionParticipantStub for us... Anyway now we are thinking to changing our port names to make this look nice..
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 ?
IMHO it's not good. After doing three major production ready releases we seriously need to think about backward compatibility ... This also broke the Kandula2 build too... ~Thilina
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
-- Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
