The latter sounds reasonable to make clients aware of violation of
protocol, but probably as a configurable option ("strict" mode?). Spec does
not tell how server should behave in these cases?
14. jan. 2014 00:21 skrev "Daniel Kulp" følgende:
>
> On Jan 13, 2014, at 2:52 PM, Jose María Zaragoza
On Jan 13, 2014, at 2:52 PM, Jose María Zaragoza wrote:
> 2014/1/13 Daniel Kulp :
>>
>> These are showing that the RelatesTo header wasn’t there or similar as it
>> couldn’t correlate the response message to a request.That is certainly
>> the cause of the “leak” as the WS-Addressing stuff
2014/1/13 Daniel Kulp :
>
> These are showing that the RelatesTo header wasn’t there or similar as it
> couldn’t correlate the response message to a request.That is certainly
> the cause of the “leak” as the WS-Addressing stuff is not seeing a proper
> response to the request.
>
Thanks Dan
On Jan 13, 2014, at 7:13 AM, Jose María Zaragoza wrote:
>
> xmlns:add="http://schemas.xmlsoap.org/ws/2004/08/addressing";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
>
>
Thanks Daniel for your reply
My testing enviroment was
Java: version 1.6.0_24, vendor Sun Microsystems Inc.
-XX:MaxPermSize=128m
-Xmx1024m
-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=true
Tomcat 6.0.23 + Apache CXF 2.7.8 + WS Addressing enabled
>Can you capture both
We’ll likely need a more reproducible test case.I just updated our
ws-addressing system test to pretty much do:
List mem = new ArrayList(12);
for (int y = 0; y < 10; y++) {
for (int x = 0; x < 5000; x++) {
greeter.greetMe("test");
}
Hello:
I'm using CXF 2.7.8 and JAX-WS to create a SOAP webservice
This webservice calls another webservice who requieres WS-Addressing
So, I declare a simple JAX-WS client with WS-Addressing enabled
http://extermal.com/Process.jpd";
bindingId="http://schemas.xmlsoap.org/wsd
