Hi, Pradeep.
Sorry for not replying promptly. Here is what I have in mind for the
Tuscany/SCA WSDL2Java tool.
1) Generate a java interface for each WSDL portType based on the JAX-WS
mapping rules (the result should be pretty much like the wsimport)
2) Allows the plug-in of databinding specific XSD2Java generators (such as
JAXB xjc or SDO XSD2Java) to generate the Java interfaces/classes from the
XSD types representing the parts for WSDL messages. The XSD2Java can
generate strongly-typed java types or weakly-typed java types (such as DOM
Node, SDO DataObject, or AXIOM OMNode).
There are existing tools from JAX-WS and Axis2 with some deficiencies:
* JAX-WS wsimport requires the WSDL has service/port. In SCA, we only
require the portType. JAX-WS wsimport only supports JAXB and there is no way
to replace it with other databindings such as SDO or AXIOM.
* Axis2 WSDL2Java is not fully JAX-WS compliant.
I'll add this project to the Apache GSoc2009 wiki [1] so that we can
collaborate to refine it as the discussions go.
[1] http://wiki.apache.org/general/SummerOfCode2009#tuscany-project
Thanks,
Raymond
From: Pradeep Fernando
Sent: Tuesday, March 24, 2009 6:56 AM
To: tuscany-dev
Subject: GSOC[2009] WSDL2Java tool for Tuscany
Hi devs,
In one of the previous mail thread Raymond suggested me to work on a code
generation tool like WSDL2java
in the Tuscany project. But he did not go in to the details of the
requirement. so this is the thoughts built on Raymonds initial idea.
I'm concentrating here on WSDL2JAVA tool for Tuscany. Already there are
tools in this domain such as Axis2 wsdl2java tool.
but the problem is the code generation done by that version of the tool is
not JAX-WS complient. for an example client-stub
generated by the tool is not jax-ws complient.
WSDL- |-data related to web-service invocation
|- message schema
Here the schema related stuff is directly related to the databinding and we
can support various kind of databinding frameworks
such as:
Jaxb,Jaxbri,XMLbeans, jibx, etc
from the data related to web-service we should generate JAX-WS compliant :
client stubs
service stubs,etc
This is my thoughts on the code-generation tool. would this be a good idea
for GSOC 2009 under Tuscany.
Is it too small for a summer project.
Any enhancement or areas i should work on?
Are there any other high priority work to be done before this. waiting for
your feedbacks. weather it is positive or negative please feel free
to give feedbacks.
Pradeep Fernando.
BTW FYI i'm preparing my project proposal on *A binding.ws implementation
based on JAX-WS Dispatch and Provider APIs* .
plz give any feedbacks on this regard in the seperate thread i have started
iin the list.
