quot; <[EMAIL PROTECTED]>
12/11/2002 05:07 AM
Please respond to axis-dev
To:
[EMAIL PROTECTED]
cc:
Subject:
RE: [wsif] WSDL2Java and WSIF
We did start talking about this a while ago
(http://marc.theaimsgroup.com/?l=axis-dev&m=103
;'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject:RE: [wsif] WSDL2Java and WSIF
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 ele
Nirmal Mukhi wrote:
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
t
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
welcom
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) an
