Dan Diephouse wrote:
James Strachan wrote:
On 22 Sep 2005, at 18:12, Dan Diephouse wrote:
James Strachan wrote:
On 22 Sep 2005, at 17:40, Sami Dalouche wrote:
Hi,
what about using Apache JaxMe project ? Is there any reason not
to consider it ?
It doesn't implement JAX-WS :) Its a JAXB implementation and I
don't know if they've ever got to JAXB 2.0 yet
(BTW the JAXB 2.0 RI rocks)
I'd use any JAX-WS implementation that actually worked :)
Celtix looks another to track. Maybe one day XFire might implement
it maybe?
I don't know of anyone who is working on this, but it could. I don't
think it would be technically that hard. There just needs to be some
company who is interested in a non-RI version of JAX WS.
Celtix is already building one - so I guess having 2 to choose from
is enough :)
Though if XFire already does JSR 181 then I don't think its that much
work to extend it to work with JAX-WS - especially if XFire can work
with JAXB 2.
Yah, I guess we're nearly there. We have JAXB 2 support and JSR 181
support. Who wants to volunteer? ;-)
Or maybe I should just remail non-JAX-WS to give ourselves some
"distinction". We could be all snobbish about it too...
:)
If you've got that much, then mostly I think its just the Service
interface (for creating clients from a WSDL), Dispatcher (to make one
way & request response calls) and then Endpoint (for deploying
implementation classes on an endpoint). So hopefuly it wouldn't take an
XFire-person too long to implement.
--
James
-------
http://radio.weblogs.com/0112098/
