Hello Asankha,
thanks for that.
I wish you a nice evening.
Jens
Asankha C. Perera schrieb:
Jens
Opps sorry.. I didn't notice the attachment.. I will check with Ruwan
on this tommorow
asankha
Jens Goldhammer wrote:
Oh, sorry, but I thought that I have attached it in the last mail! Do
you want to have the complete project with all libs?
I have attached the zip-file with the client-source again...
Jens
Asankha C. Perera schrieb:
Jens
maybe you have not got all mails from the mailing list?
Ruwan already answered me:
Nope.. I think Synapse replies correctly and there isn't a bug..
Again, your client code will be helpful
asankha
---------------
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
---------------------
Nevertheless I have attached the client-code
(client-implementation, axis2.xml, callbackhandler, wsdlfiles)-
please don?t look at the quality. It is only for testing purpose :-)
I think the new injected message-id from synapse to the client on
the response way is not correct (compare with the response from
tomcat to esb). I don?t know if this influences the client
behaviour...
Thanks,
Jens
Asankha C. Perera schrieb:
Jens
I think the interaction is correct and do not see anything wrong
in the reply received by the client.. unless it was expecting the
reply on 192.168.88.1:8200.. can you share your client code as a Zip?
asankha
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
------------------------------------------------------------------------
_______________________________________________
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
------------------------------------------------------------------------
_______________________________________________
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
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
