JAXRPC 2.0 will include asynchronous messaging-
Stay tuned...
Aysu Betin wrote:
>
> Thanks for bringing up this question.
> It is just what I wanted to learn.
> Why is JAXM going away?
> As far as I understand JAX-RPC does synchronous messaging
> (it is implied in the name "remote procedure call")
> I think asynchronous messaging is more sutiable
> for web service applications.
>
> aysu betin-can
>
>
> Karr, David wrote:
>
>> I've noticed the JAXMServlet class, which appears to have been defined
>> in JWSDP 1.1, but doesn't appear to be in the later specifications. The
>> Javadoc for this class indicates that it's not really supported, and may
>> not be present in an actual implementation.
>>
>> Besides the fact that it's not present after JWSDP 1.1, are there any
>> particular risks (or considerable value) from using this class as a
>> "lightweight" web services interface (as opposed to the more
>> "heavyweight" jaxrpc interface (using a "web-services.xml" descriptor)?
>>
>> Does anyone know if the latest WebSphere release uses this class? It's
>> present in the latest WebLogic release.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
>> For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net