Thank you for your fast answer!
On Wed, 13 Jan 2010 15:56:40 -0500
Daniel Kulp <[email protected]> wrote:
> 1) OneWayProcessorInterceptor stuff - not needed. Thats for the the
> server side stuff only.
Ok, I removed those two interceptors. There was no change in the error,
however.
> 2) Does the registration method on the IEventService interface have
> the proper @OneWay annotation on it? If not, it wouldn't be
> considered a one way at all.
It has a @Oneway annotation, using @OneWay generates a compile-time
error (cannot find symbol).
> 3) Even with a one way, per spec, we have to wait till the server
> sends back the 200 or 202 response. If the server is not sending
> that back immediately upon receipt of the message, that's a bug on
> the servers side.
It does not answer anything, I can see that with tcpdump. Is there a
workaround for that, or there is nothing to do to handle .NET's
misbehaviour?
Does anyone have experience in integrating with one-way MS web
services? Or MS web services in general?
By the way, I am using cxf 2.2.5.
Thanks for your answer in advance!
PP
