Ias,
We have started looking at the SEI model for the endpoints, but don't have a schedule laid out yet. One of the things we need to do here is understand a little more the work that Rajith has been getting started on with respect to JSR-181 support using WSM/Beehive. It seems like there is enough commonality between the JAX-WS endpoints and the Axis2 endpoints that portions of the work could be shared across both.
Because of the heavy use of annotations this work should probably coincide with the work for the JAX-WS proxy client support.
Thanks for the interest.
Regards,
Nicholas Gallardo
WebSphere - WebServices Development
[EMAIL PROTECTED]
Phone: 512-838-1182
Building: 901 / 5G-016
| Changshin Lee <[EMAIL PROTECTED]>
06/16/2006 07:33 PM
|
|
Thanks for your great contribution. Do you have any plan (and schedule)
to start SEI model such as from Java and from WSDL apart from MOM model?
Cheers,
Ias
> The IBM Web services team has been developing a JAX-WS 2.0
> implementation that we will contribute to Apache, which uses Axis2 as
> it's core runtime. It is an initial drop, but we intend to continue
> this development in Apache open source. Given the increased interest
> that has been displayed on the mailing list, we will be opening a JIRA
> issue with a patch containing code that we would like to have
> considered for contribution as a jumpstart for the support.
>
> This is just a first pass and is intended to be a starting point to
> allow the Apache community involvement. The IBM Web services team
> would like to participate in building a JAX-WS 2.0 implementation in
> conjunction with the Apache community.
>
> Developers that have participating in developing this drop, and are
> planning to continue are the following:
>
> Nick Gallardo
> Rich Scheuerle
> Jeff Barrett
> Nikhil Thaker
> Mike Rheinheirmer
> Brent Ulbricht
> Dan Sedov
> Lizet Ernand
> Samuel Isokpunwu
>
>
> Code structure:
>
> This code has been built as a module under the Axis2 root in
> modules/jaxws.
> - Maven enabled
> - Java 5 enabled
> - Verification tests included (many more to come)
>
> As we've started developing this code, the goal has been to re-use as
> much of the underlying Axis2 runtime as possible. This includes
> making use of the existing ServiceClient API on the client and the
> MessageReceiver API for services.
>
>
>
> Contents:
>
> Client
> -------------------
> Support for JAX-WS javax.xml.ws.Dispatch
> * Parameter types supported:
> - JAX-B (using JAXBContext)
> - javax.xml.transform.Source (StreamSource, DOMSource, SAXSource)
> - String (non-spec)
>
> * Invocation patterns supported:
> - sync: invoke
> - one-way: invokeOneWay
> - async: invokeAsync (callback only)
>
> * Usage modes
> - PAYLOAD (SOAP Body contents)
> - MESSAGE (the entire SOAP Envelope)
>
>
> Service
> -------------------
> Support for javax.xml.ws.Provider style endpoints
> * Parameter types
> - javax.xml.transform.Source (StreamSource, DOMSource, SAXSource)
> - String (non-spec)
>
> * Usage modes
> - PAYLOAD only (MESSAGE requires annotations support for
> javax.xml.ws.ServiceMode)
>
>
>
> Development activity in progress:
>
> * SAAJ SOAPMessage support for both the Dispatch and Provider
> * Fault processing
> * Attachments
> * SOAP 1.2 support
> * Annotations support for Provider
> * JAXWSMessageReceiver with support for pluggable dispatchers and server
> side application handlers
>
>
> Again, this is our first step here. We look forward to working with
> the Apache Web services community on furthering this implementation.
> We welcome the community's feedback.
>
> Regards,
>
> The IBM Web services team
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
