axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Commented: (AXIS-2287) Alternative approach for stub generation
Date Fri, 04 Nov 2005 12:07:21 GMT
    [ ] 

Davanum Srinivas commented on AXIS-2287:

" - The Java interface definine the API for the stubs " is done using Java2WSDL. So the recommendation
is to start with Java2WSDL, then run all the tools you want/need like WS-I stuff and get the
exact WSDL you want with the exact schema. If you see the sample for xbeans i added, you can
see that it takes the WSDL and Schema but it does not generate any classes from the schema
and generates code for the web service itself and uses the classes generated by xmlbeans.
THis is exactly what you want. only thing missing is specifying the serializerfactory deserializerfactory
in the wsdl2java ant task. I can whip it up quickly but folks will have to wait for another
release. Similar support is already in Java2WSDL ant task (classes and factories for them)
with the complextype element. 


> Alternative approach for stub generation
> ----------------------------------------
>          Key: AXIS-2287
>          URL:
>      Project: Apache Axis
>         Type: New Feature
>     Versions: future (enh)
>     Reporter: Guy Rixon
>     Priority: Minor

> The current WSDL2Java generates Java beans for message parts and stubs that use those
beans (and, by extension, the Axis serializers/deserializers). The API into the stubs is defined
by WSDL2ava and tends to change slightly between Axis version when complex messages are used.

> Many projects like to use their own serializer/deserializer systems, typically Castor
or XMLbeans. This is possible with Axis but WSDL2Java does not support it. Many projects would
benefit from fixed stub APIs that do not change across Axis versions.
> I suggest an alternative to WSDL2Java that takes three things as input:
>   - The WSDL contract
>  - The Java interface definine the API for the stubs
>  - A list of mappings between classes and XML types.
> The latter would probably have to state both the class name and binding mechanism for
each XML type: it would have to identify the serializer and deserializer factory for the type.
Isuspect that this would be an XML document, not a simple properties file.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message