Selon James Strachan <[EMAIL PROTECTED]>:

> 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).

Different implementations of the same standard is definitely a good thing
(especially with truly free licenses, I'm not sure what the CDDL allows me to
do.. yeah, another thing to read about ;p). But it looks like the .Net way of
exposing web services is the approach most people prefer, and JSR 181 + JAX-WS
+ JAXB 2.0 seems to be the nearest equivalent. So let's hope there's going to
be a consensus about this.

>
> 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.

OK Nice ! You mention ActiveSOAP in one of your previous emails to me (yeah,
sorry, I'm sollicitating you a lot...), that would allow me to marshall POJOs
and talk to my BPEL process for example. Is this unique to ActiveSOAP, or is it
also available in AXIS + XFire ? (I definitely want to try to avoid using 10
different libraries to do the same things.. Otherwise, the poor guys that are
going to maintain / enhance my code are going to die ;)
Anyways, I'll probably try to create some documentation about the technology I
used so that other programmers can understand what I did. (like everybody I
guess, I'm just running out of time..) I'll clearly separate it from the design
documents so that I can post it here, more documentation is definitely a must
for everybody.

>
> 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.
>

nice :)

Regards,
Sami Dalouche




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Reply via email to