Apart from building WSDL object model, i think we have little in common across languages in terms of emitting code. For example Javascript and Java might not share anything in the code pattern or file pattern for generated code. So what are we abstracting out into WSDL2WS?
- Venkat On 5/26/05, Glen Daniels <[EMAIL PROTECTED]> wrote: > > Axis1 does have the "generic" WSDL2 classes and the more specific Java ones, > and was in fact designed with exactly the same idea (generating stubs/skels > for multiple languages). I would prefer something like "WSDLCodeGenerator" > or "WSDL2Code" over "WSDL2WS", just because I think it'd be easier to > understand. > > --Glen > > ----- Original Message ----- > From: "Sanjiva Weerawarana" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wednesday, May 25, 2005 7:46 PM > Subject: Re: [Axis2] WSDL2Java renamed? > > > > Hi Tom! > > > >> > Renamed the WSDL2Java to WSDL2WS > >> > >> Sorry to jump in late here. I am really not a fan of naming the command > >> WSDL2WS. What does 'WS' mean? Is this generating Java code? Notice > >> that Axis 1.x has the WSDL2 structure, which allows you to implement > >> other language back ends. > > > > The reason it was changed is because it allows multiple target langs to > > be generated. Right now Ajith has it generating C# stubs as well and has > > run Axis2 inside .Net with IKVM and used the stubs from other .Net > > stuff. > > > >> I am -1 on changing the name of a tool as basic as WSDL2Java. > > > > I'm ok with having a convenience class called WSDL2Java that sets the > > target language to Java. However, we do need a name for the basic thing > > which is capable of producing whatever language. (The code generator > > uses XSLT stubs actually.) > > > > What name do u suggest for the basic thing? > > > > Sanjiva. > > > > > > >
