Chinthaka,
Rich and I had discussed yesterday putting something together that explains some of what we're trying to do. Unfortunately, some of those ideas aren't reflected in the code yet so a document is the best place to start. We'll put something together and will post it to the list in the early part of next week.
Thanks to all for the reception. We're looking forward to working with the team on this.
Regards,
Nicholas Gallardo
WebSphere - WebServices Development
[EMAIL PROTECTED]
Phone: 512-838-1182
Building: 901 / 5G-016
| Eran Chinthaka <[EMAIL PROTECTED]>
06/17/2006 02:18 AM
|
|
Hi Nicholas and IBM team,
I'd say this is great work.
I'd like to see some explanation on how this is implemented on Axis2. I
agree that code is the best document, but if we can have an explanation,
it will be very easy for all of us to understand it and help within a
short period of time. Perhaps the guys here knows Axis2 internals better
than anyone else, there can be improvement suggestions as well.
Can one of you please volunteer to do that? I know that will be a big
document, but it will be beneficial.
(One additional question. If this yet another module and if it requires
jdk5, then we need to do a small trick for people using jdk14 to not
have problems. I think Dims had already done to one of the modules.)
-- Chinthaka
Nicholas L Gallardo wrote:
> 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
>
signature.asc
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
