Hmm now I use version 2.1.4 and I still have the same behaviour. But you
think, it's fixed now?
This is now fixed on trunk/2.1.x.
Dan
Dan
On Thu February 12 2009 11:48:27 am Daniel Kulp wrote:
On Wed February 11 2009 7:27:47 am hairman wrote:
I'm trying to use the
On Thu February 19 2009 9:44:15 am hairman wrote:
Hmm now I use version 2.1.4 and I still have the same behaviour. But you
think, it's fixed now?
2.1.4 was tagged/built on Feb 5. The fix wasn't done till the 12th. Thus,
it wouldn't be in 2.1.4.I'll get new snapshots for 2.1.5 up today.
I just published a 2.1.5-SNAPSHOT.
On Thu, Feb 19, 2009 at 10:19 AM, Daniel Kulp dk...@apache.org wrote:
On Thu February 19 2009 9:44:15 am hairman wrote:
Hmm now I use version 2.1.4 and I still have the same behaviour. But you
think, it's fixed now?
2.1.4 was tagged/built on Feb 5. The
On Thu February 12 2009 1:36:39 pm Daniel Kulp wrote:
This is actually a server side issue, not a client side issue. The client
is doing the correct thing. Per spec, it has to wait for the 200/202
response codes to make sure the message was successfully sent. However,
the server wasn't
On Wed February 11 2009 7:27:47 am hairman wrote:
I'm trying to use the @Oneway-Annotation in a CXF Serviceinterface using
Spring. @OneWay (camelCase) doesn't exist, so I think, it's a fault in the
CXF docu? (
http://cwiki.apache.org/CXF20DOC/developing-a-service.html#DevelopingaServi
This is actually a server side issue, not a client side issue. The client is
doing the correct thing. Per spec, it has to wait for the 200/202 response
codes to make sure the message was successfully sent. However, the server
wasn't sending the code back until after the invoke.I'm
I'm trying to use the @Oneway-Annotation in a CXF Serviceinterface using
Spring. @OneWay (camelCase) doesn't exist, so I think, it's a fault in the
CXF docu? (
http://cwiki.apache.org/CXF20DOC/developing-a-service.html#developingaservice-the%257b%2...@oneway%257d%257dannotation
)
I import
