be a
problem, but I could then run a series of extra tests and such for it.
Dan
Thanks,
Jesse
-Original Message-
From: Jesse Pangburn
Sent: Friday, June 28, 2013 3:05 PM
To: users@cxf.apache.org; Daniel Kulp
Subject: RE: how to determine/debug effective ws policy used?
Hi Dan,
Just
(find.dispatch.operation, Boolean.TRUE);
thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Tuesday, September 10, 2013 2:14 PM
To: users@cxf.apache.org; Jesse Pangburn
Subject: Re: how to determine/debug effective ws policy used?
On Sep 9, 2013, at 6:57 PM
: Wednesday, June 05, 2013 3:36 PM
To: Daniel Kulp; users@cxf.apache.org
Subject: RE: how to determine/debug effective ws policy used?
Hi Dan,
As always, thanks for your excellent help! That did work. However, there's a
setting that I thought was supposed to take care of this issue in Dispatch
To: Daniel Kulp; users@cxf.apache.org
Subject: RE: how to determine/debug effective ws policy used?
Hi Dan,
As always, thanks for your excellent help! That did work. However, there's a
setting that I thought was supposed to take care of this issue in Dispatch:
disp.getRequestContext().put
This appears to be a bug. I stepped through the debugger into the
PolicyOutInterceptor's handle method and found the following in the
BindingOperationInfo object:
[BindingOperationInfo: {http://cxf.apache.org/jaxws/dispatch}Invoke]
This is the default value which gets overridden at some point
On Jun 5, 2013, at 4:46 PM, Jesse Pangburn jesse.pangb...@infor.com wrote:
This appears to be a bug. I stepped through the debugger into the
PolicyOutInterceptor's handle method and found the following in the
BindingOperationInfo object:
[BindingOperationInfo:
