cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse" <...@envoisolutions.com>
Subject JAX-WS 2.1 and JAX-WSA [was Re: Next Release]
Date Tue, 02 Jan 2007 04:07:58 GMT
I want to fork the thread a minute here to address an issue Ted brings up.

Do we want to target JAX-WS 2.1 instead of 2.0 [1]? I believe the spec will
be finalized by the time we do our 2.0 release. Doug Kohlert's blog
mention's 3 principle changes [2]:
1. Support for WS-Addressing when creating endpoints and dispatches
2. Support for type substitution. This is supported by adding an @XmlSeeAlso
attribute which specifies additional classes to be added to the JAXB
context. (You'll notice a user ran into that issue on the user's list a
couple days ago)
3. Feature enablement - i.e. there is a MTOMFeature and AdressingFeature.
Not really sure how this works yet, but sounds very useful...

Along with this, it would be interesting to start on JAX-WSA - or at least
got started on it. JAX-WSA is just a few annotations for WS-Addressing and
some interfaces for representing EPRs [2].

What does everyone think? JAX-WS 2.1 at least seems to solve some important
issuse at least, so I would be +1 for going ahead and targetting it.

- Dan

1. http://jcp.org/aboutJava/communityprocess/maintenance/jsr224/index.html
2. http://weblogs.java.net/blog/kohlert/archive/2006/11/jaxws_21_mainte.html
3. https://jax-wsa.dev.java.net/nonav/javadocs/ed2/index.html

On 1/1/07, Ted Neward <ted@tedneward.com> wrote:
>
> Hey, guys, some thoughts for a v.Next release from one who's principally a
> user, not a toolkit developer:
>
> (*) The samples definitely need some fleshing out, in that most of them
> come
> from the same perspective (that of WSDL/Contract-first). Not everybody
> writing XML services is going to want to take the hit of learning WSDL, so
> something that demos an approach that's "code-first, contract-aware",
> IMHO,
> is going to go over well.
>
> (*) How about demos-and/or-support for SOAP-over-SMTP/POP3? And/or
> SOAP-over-UDP? And other transports come to mind, such as Jabber/XMPP.
>
> (*) Small nit: Make SOAP 1.2 the default for java2wsdl. Please. SOAP 1.1is
> dead (for which we should all give thanks), let's let it rest in peace.
>
> (*) A WS-Eventing implementation would be VERY cool. (Had I the time, I
> would step up here and volunteer to build it, but alas....)
>
> (*) Ditto for WS-Discovery.
>
> (*) I don't currently see any support for WS-Addressing anywhere thus far;
> am I just not looking in the right places, or is this something that
> you're
> waiting on JAX-WSA to finish up before shipping, or....?
>
> Feel free to ignore any or all of these, of course. :-)
>
> Ted Neward
> Java, .NET, XML Services
> Consulting, Teaching, Speaking, Writing
> http://www.tedneward.com
>
>
> > -----Original Message-----
> > From: Dan Diephouse [mailto:dan@envoisolutions.com]
> > Sent: Sunday, December 31, 2006 2:22 PM
> > To: cxf-dev@incubator.apache.org
> > Subject: Re: Next Release
> >
> > Two things I want to add to my list:
> > - WSDL 2 support - or at the very least enough of it implemented that we
> > can
> > put it in 2.1 without changing APIs.
> > - Commons HTTP client support. Right now we don't support the myriad of
> > authentication schemes needed. Commons HTTP is proven and I think we
> > should
> > support it (even if it is synchronous...)
> >
> > On 12/31/06, Dan Diephouse <dan@envoisolutions.com> wrote:
> > >
> > > Hi All,
> > >
> > > Well it seems we managed to get our first release out successfully! So
> I
> > > suppose its time to start thinking about the next release.
> > >
> > > I personally would like to see us target our next release to be a
> > 2.0release candidate. Our code is definitely maturing now and I think
> > we'll be
> > > ready. However, we have some major areas which I see us needing to
> > finish
> > > before then:
> > >
> > >    - JAX-WS TCK
> > >    - Tooling Refactor
> > >    - Port XFire Aegis databinding library
> > >    - WS-Security & SecureConversation
> > >    - Async HTTP Server support [1]
> > >    - Async HTTP Client support [2]
> > >    - Support content based routing
> > >    - Soap w/ Attachments
> > >    - HTTP Binding Client
> > >
> > > Anyone else have any areas I missed? I would be very wary about doing
> a
> > > release without any of those items done I think. In addition to those
> > they
> > > are lots of smaller issues we need to think about. For example:
> > >
> > >    - Configuration (still haven't heard back on my proposal, will
> > >    kickstart this thread in a bit...)
> > >    - Binding discovery
> > >    - RM and removal of interceptors
> > >    - Code cleanup
> > >    - and a gazillion other JIRA issues
> > >
> > > Seeing that its nearly the new year, I think this puts us on track to
> > > start talking about actually doing a release on or around March 1. All
> > > depends on how quickly we work though :-)
> > >
> > > Thoughts?
> > >
> > > - Dan
> > >
> > > 1. I believe this will be part of the Jetty 6 port Willem is doing.
> > > 2. I need to check and see what the status of the Jetty 6 HTTP client
> is
> > > yet
> > >
> > > --
> > > Dan Diephouse
> > > Envoi Solutions
> > > http://envoisolutions.com | http://netzooid.com/blog
> > >
> >
> >
> >
> > --
> > Dan Diephouse
> > Envoi Solutions
> > http://envoisolutions.com | http://netzooid.com/blog
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.5.432 / Virus Database: 268.16.1/611 - Release Date:
> 12/31/2006
> > 12:47 PM
> >
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.432 / Virus Database: 268.16.1/611 - Release Date: 12/31/2006
> 12:47 PM
>
>
>
>


-- 
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message