Hi devs,
I've been exploring the Axis2 WSDL2Java tool and its architecture.
Let me explain the high level Architecture of the WSDL2Java codegen tool
used by Axis2.
say we invoke it using a WSDL and few options. the sequence is like this.
1. first it goes through a option parser, where it figures out different
options given by the user.
2.then it goes to the code_generation_Engine where most of the stuff
happens. there
* the schema's taken from the WSDL fed in to a schema compiler(can
be any schema compiler) and get the generated classes with mappings.
* the web-services related things frd in to the
WSDLToAxisServiceBuiler class and get a AxisService related to given WSDL.
3.after that these info is pumped in to a intermediate xml file according to
a given known template.
4.Since all the Info about the service is available in the intermediate xml
it can be converted in to any language. you just have to use different XSL
templates to
do that.
So this is about Axis2 one, So one for tuscany should have JAX-WS
compatibility. I looked in to the wsimport tool. there using a different
web-services stack.
As i know Tuscany uses Axis2 as its ws.binding. I'm having concerns about
underline web-services stack. I think it comes to play in this tool. correct
me if i am wrong.
Now there is a GSOC project listed under binding.ws to provide JAX-WS based
implementation instead of AXIS2. Any comment on this?
if I'm not clear enough plz feel free to ask questions,
your feedbacks are mostly welcome.
Pradeep Fernando.
p.s - sorry for the last mail. it was a mistake.
