Rich, is that tooling accessed directly via wsdl2java or used externally?
In any case, +1 to not killing RI tooling! We use that for JAXB support
anyway.
Sanjiva.
R J Scheuerle Jr wrote:
Thanks Sameera,
Currently the Sun provided JAX-WS tooling and engine are used for the
JAX-WS layering.
There are a number of corner cases. Wrappering is one such issue.
It will be important as we go forward to ensure that the existing
support for the Sun tooling/ri continues to work.
Question: How can the existing JAX-WS developers assist or provide
feedback for this effort ?
Thanks,
Rich Scheuerle
IBM Web Services
Apache Axis2 ([EMAIL PROTECTED])
512-838-5115 (IBM TL 678-5115)
"Sameera Jayasoma" <[EMAIL PROTECTED]> wrote on 07/03/2007
09:08:44 PM:
>
>
> ---------- Forwarded message ----------
> From: Sameera Jayasoma <[EMAIL PROTECTED]>
> Date: Jul 4, 2007 6:54 AM
> Subject: JAX-WS 2.0 support for Apache Axis2 WSDL2Java Code Generator
> To: [email protected]
>
> Hi all,
>
> I'm working on implementing JAX-WS 2.0 support for Apache Axis2
> WSDL2Java Code Generator for Google Summer of Code 2007. My
> proposal can be viewed at http://wiki.apache.
> org/general/SameeraJayasoma/SummerOfCode/2007.
>
> Here is the description of the design I have followed after having
> several discussions with the mentor.
>
> Java API for XML Web Services (JAX-WS) is a technology designed to
> standardized the construction of web services and web service
> clients in Java. JAX-WS 2.0 describes set of mappings from a service
> defined in a WSDL to Java classes and vice versa. JAX-WS 2.0
> delegates the data binding related-task to JAXB 2.0. These mappings
> are somewhat different from the from the way how Axis2 maps WSDL
> constructs to Java constructs. Therefore I came up with a
> JAXWSEmitter class which extends the
> AxisServiceBasedMultiLanguageEmitter class. This way I could reuse
> some of the functionalities.
>
> JAX-WS defines two styles which are non-wrapper style and wrapper
> style to map the contents of input and output message to Java method
> parameters.
> There are some rules for which a WSDL:Operation to qualify for
> wrapper style mapping. wrapper style mapping specifies more or less
> the same convention which is followed in SchemaUnwrapperExtension
> class. But there are some variations. Therefore I decided to add a
> new extension class called JAXWSWapperExtension.
>
> I'm currently working on a issue found when implementing the
> JAXWSWapperExtension. Existing implementation of Jaxbri does not
> support unwrapping.
>
> I will send a patch within two days after completing some minor things.
>
> Any improvement to the existing design is greatly accepted.
>
> Thanks in advance
>
> Sameera
>
> --
> Sameera Jayasoma
> http://sameera-jayasoma.blogspot.com/
> http://www.flickr.com/photos/sameera-jayasoma
>
> --
> Sameera
> http://sameera-jayasoma.blogspot.com/
> http://www.flickr.com/photos/sameera-jayasoma
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
