axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Elder" <>
Subject RE: [wsif] WSDL2Java and WSIF
Date Wed, 11 Dec 2002 10:07:43 GMT

We did start talking about this a while ago
( , but as
AXIS 1.0 was just coming out it got left.

Ideally WSIF needs two things:

- A WSDL2Java like tool to generate the service interface and complex type
classes from a WSDL file

- An xxx2WSDL tool which can generate WSDL with bindings for all the
different bindings WSIF has providers for.

As far as I can tell WSDL2Java from AXIS 1.0 only outputs the service
interface and complex type classes when there is a soap binding in the
WSDL. Are you saying this is wrong and I should raise a bug for it?

Another problem with WSDL2Java is when the WSDL has a WSIF SOAP over JMS
binding and service port, WSDL2Java crashes with an exception as it can't
find the endpoint address in the service port - probably because the WSIF
SOAP/JMS service port has jms:address not  soap:address. It does still
output the service interface and type classes so this isn't such a problem,
but doesn't look so nice. A bugzilla ? or perhaps if we can merge the AXIS
JMS async work and WSIF SOAP/JMS to be the same then I guess this may get

I don't think anyone's looked at an xxx2WSDL tool yet.


Anthony Elder
Web Services Development
IBM UK Laboratories,  Hursley Park
(+44) 01962 818320, x248320, MP208.

Tom Jordahl <> on 10/12/2002 20:05:35

Please respond to

To:    "''" <>
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 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  []
Sent: Tuesday, December 10, 2002 3:01  PM
Subject: [wsif] WSDL2Java and  WSIF


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.


View raw message