Sanjiva, Java2WSDL means more that the commandline tool. It is used at runtime to generate WSDL from a composite of information from typemapping, deployment descriptors (maybe annotations) etc. Basically if we drop a POJO, we should be able to generate a wsdl for it at runtime. Yes, we'd have to let admins configure either wsdl1.1 or wsdl2.0 (or) set up an alternate url "?wsdl20" for wsdl2.0 and keep "?wsdl" for wsdl1.1.
Are you ruling this out for Axis2? -- dims On 8/4/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > On Thu, 2005-08-04 at 08:30 -0400, Tom Jordahl wrote: > > You can't get anywhere near a 1.0 release (Beta or otherwise) without > > Java2WSDL functionality, right? > > > > Is anyone working on this? WSDL 2.0 support would be a *huge* incentive > > for non-Axis users to give Axis2 a try. Of course you need Java2WSDL > > because nobody knows how to write WSDL 2.0 yet... > > > > Maybe WSO2 (Sanjiva's new company) will step up and do the WSDL 2.0 > > work? > > :-) > > ;-) > > But we have a great tool for that already!!!!!! > > Its the Axis 1.x Java2WSDL tool .. > > Is there any reason to re-write that for WSDL 1.1?? To support WSDL 2.0 > I'd rather see it being re-done (to not have to force another download) > or we can look at some metadata stuff but for WSDL 1.1 we have the > problem solved thanks to you and the other Axis1 contributors :). > > Sanjiva. > > > > -- Davanum Srinivas -http://blogs.cocoondev.org/dims/
