Currently, if I have a WSDL with a non-soap binding (e.g. ejb/jms binding), WSDL2Java does not produce the service interface correctly. Note that it correctly generates the java types specified in the types section of the WSDL, but the portType interface is not generated.
My question was regarding the portType generation. Shantanu --- Paul Fremantle <[EMAIL PROTECTED]> wrote: > WSIF should work with the JAX-RPC interfaces that > WSDL2Java creates. > > As Sanjiva says, the bindings shouldn't affect the > interface. > > Paul > > On 6/10/05, Sanjiva Weerawarana > <[EMAIL PROTECTED]> wrote: > > I doubt that kind of work being done on the 1.2.x > path at this point .. > > > > For Axis2, I'd like to look at doing a WSIF2 on > top of AXIOM. However, > > I'm not clear why that WSIF affects the > types/interfaces - the WSIF > > binding details go inside the stub. What I'm > suggesting is that with > > AXIOM we now have a universal way to propagate > data inside WSIF > > (essentially to re-do WSIFMessage). We did this a > while back with > > something called JROM, but JROM never made it out > of AlphaWorks due to > > IBM change of heart. > > > > Sanjiva. > > > > On Thu, 2005-06-09 at 17:47 -0700, Shantanu Sen > wrote: > > > Is there any plan to augment WSDL2Java so that > it can > > > understand and generate types/interfaces for > WSDL that > > > contains (non-SOAP) binding extensions as > defined by > > > WSIF e.g. ejb, jms etc? > > > > > > I am asking this question in the context of both > Axis > > > 1.2.x and Axis 2. > > > > > > Thanks, > > > Shantanu Sen > > > > > > > >
