Hi Eamonn
Perhaps you can do the same way the (out) logging interceptor does it ? Can
it capture the outbound message on the client side ?
connection.getResponseCode()
I thought your latest patch has fixed it ?
thanks, Sergey
Eamonn Dwyer-2 wrote:
Hi
is there a way of getting the
Hi Sergey
the LoggingOutInterceptor can capture the data from various locations (from the
message) and build up a log representing the outbound request but I dont think
its the EXACT data being sent to the server as the HTTP request. I am writing
an interceptor that monitors the data passed
Last night, I committed a bunch of changes that added an event listener to the
FactoryBeans and added a bunch of events out of the beans to the listener.
There are a couple of purposes for this:
1) I'm hoping to simplify some of the stuff in RSFB. I'm planning on
allowing the databinding
Hi Dan,
given that I still need to look at the code... here are 2 things that
come to my mind...
Daniel Kulp wrote:
@WSDLDocumentation - this is a START of being able to add some documentation
nodes to the generated wsdl. It's not really working well yet, but it at
least is a starting
On Fri August 7 2009 1:20:23 pm Alessio Soldano wrote:
Daniel Kulp wrote:
@WSDLDocumentation - this is a START of being able to add some
documentation nodes to the generated wsdl. It's not really working well
yet, but it at least is a starting point. Most likely, I'll need to
break this
Daniel Kulp wrote:
On Fri August 7 2009 1:20:23 pm Alessio Soldano wrote:
Daniel Kulp wrote:
@WSDLDocumentation - this is a START of being able to add some
documentation nodes to the generated wsdl. It's not really working well
yet, but it at least is a starting point. Most likely,
On Fri August 7 2009 1:44:12 pm Alessio Soldano wrote:
Daniel Kulp wrote:
On Fri August 7 2009 1:20:23 pm Alessio Soldano wrote:
Daniel Kulp wrote:
Now, @WSDLDocumentation on a method does that document the portType
operation, the binding operation, the response message, the return
