Hi Jens,
Again this is an issue existed on the 1.6 release of ESB (that is with
synapse 1.1.1) and we are in the process of fixing this issue (adding a
new message id). I will let you know once we are done with the fix so
that you could try the nightly build of ESB.
I am 90% sure that this is the issue, which caused your problem.
Thanks,
Ruwan
Jens Goldhammer wrote:
Hello,
I have build up very easily with the wso2 esb (thanks for that good
graphical user interface for build the mediations!), but I am running
into problems with ws-adressing enabled.
Following scenario:
client <-> esb <->tomcat
The client does not get the answer in the callbackhandler although the
message is delivered from synapse to the client.
I have used tcpmon to investigate the messages and I think the
response from synapse to the client is not like the client it expects.
Only an assumption! In my eyes, Synapse should not inject a new
message-id...
Please have a look at these files and the synapse config for the proxy
if anything is wrong...
Thanks,
Jens
------------------------------------------------------------------------
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
