WSDL2Java in Axis was designed to produce the correct JAX-RPC artifacts
in the face of incomplete WSDL.
So we
should in fact generate the right Java files even if there is no service element
or SOAP binding. This may have gotten broken, but if so it needs to be
fixed.
Paches
welcome!
--
Tom
Jordahl
Macromedia Server Development
-----Original Message-----
From: Nirmal Mukhi [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 10, 2002 3:01 PM
To: [EMAIL PROTECTED]
Subject: [wsif] WSDL2Java and WSIF
From: Nirmal Mukhi [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 10, 2002 3:01 PM
To: [EMAIL PROTECTED]
Subject: [wsif] WSDL2Java and WSIF
Hi,
At some point we need to work on getting WSDL2Java to do the right thing with WSDLs as far as WSIF is concerned. Just to jot down TODO tasks for the future:
1. Suppress generation of Axis-specific code by WSDL2Java
2. Generate java equivalents of port types (the JAX RPC service interface) and complex schema types even if the WSDL does not contain a service element, or contains a service element with no SOAP port.
Basically we need something that follows JAX-RPC rules and operates on the abstract service description alone, without even looking for bindings, the service element, etc. Hopefully it should be easy to customise WSDL2Java to do this. Also would be nice to package such a tool along with WSIF - right now we'll be forced to point users elsewhere, but since current tools assume so much about the structure of a WSDL - such as the existence of a SOAP binding - users might have a hard time finding a suitable tool.
Nirmal.
