Hi,
I use the jax-ws Provider mechanism to implement a service provider:
@WebServiceProvider
@ServiceMode(value = Service.Mode.MESSAGE)
public class SOAPProvider implements ProviderStreamSource
If WS-Addressing is enabled and I receive a message with a ReplyTo address,
then the server will
You can use WS-ReliableMessaging for this:
http://cxf.apache.org/docs/ws-reliablemessaging.html
- Dennis
Dennis M. Sosnoski
Java Web Services Consulting http://www.sosnoski.com/consult.html
CXF and Web Services Security Training
http://www.sosnoski.com/training.html
Web Services Jump-Start
: Dennis Sosnoski [mailto:d...@sosnoski.com]
Sent: Wednesday, November 20, 2013 12:06 PM
To: users@cxf.apache.org
Subject: Re: long running asynchronous service provider
You can use WS-ReliableMessaging for this:
http://cxf.apache.org/docs/ws-reliablemessaging.html
- Dennis
Dennis M. Sosnoski
Java
In general, once the message patterns become longer than about 30 seconds, I
would recommend completely rethinking the problem. It’s no longer really a
request/reply style invocation and likely shouldn’t be modeled as one. At
that point, I’d recommend one of a couple solutions:
1) Return
asynchronous service provider
In general, once the message patterns become longer than about 30 seconds, I
would recommend completely rethinking the problem. It's no longer really a
request/reply style invocation and likely shouldn't be modeled as one. At
that point, I'd recommend one of a couple
to understand all the pros and cons.
Thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Wednesday, November 20, 2013 1:51 PM
To: users@cxf.apache.org; Jesse Pangburn
Subject: Re: long running asynchronous service provider
In general, once the message patterns become
