On 2 Sep 2005, at 15:00, Sami Dalouche wrote:
Hi,
Totally agreed! :) Its our bad for having bad examples/
documentation.
Hopefully these will get much better as time goes on so it won't be
such an effort to find your feet and get going with this stuff.
BTW I've just updated the website to reflect the latest JAX-WS / JAXB
2.0 implementation of WS-Notification with proper links to the
javadoc
and some example code...
http://servicemix.org/WS+Notification?refresh=1
OK, thanks !
OK, so now, it looks like there are like a hundred different ways
of exposing a
class as a web service. Let's hope XFire + the others will focus on
JAX-WS and
there this becomes THE way to expose a web service.. all of this is
a little
confusing ;) ActiveSOAP, XFire, Axis, I can barely feel the
difference. (I'm
probably not the only one..)
Yeah its confusing :)
For now we're trying out the JAX-WS RI for our WS-* implementations.
I'm sure there will be a few different implementations of JAX-WS -
sometimes choice is a good thing. Though certainly we're recommending
folks program to the JAX-WS model (JAXB 2.0 for marshalling, JSR 181
annotations for WS stuff and for service invocation/hosting glue, JAX-
WS APIs).
I think XFire can/will support JAX-WS (or at least JSR 181
annotations) - I'm not sure if its implemented the JAX-WS APIs
(Service/ServiceFactory, Endpoint/EndpointFactory etc). One day Axis
2 might implement JAX-WS and there could be other stacks coming along
too I hope.
The nice thing is from an application developer you just depend on
JAX-* standards (javax.*) stuff and your code, in theory should be
deployable in various stacks.
James
-------
http://radio.weblogs.com/0112098/
