I found how to make it async. I had to remove the
Know, I have another problem. The response isn't sent correctly to the reponse address (wsa-replyTo)
1. client sends message to ebws with wsa-replyTo header
2. ebws responses http 202 with empty message
3. ebws does some action and generates a new message
4. when ebws finishes it responds and empty message to wsa-replyTo EPR
in this scenario the message generated in step 3 which is the correct message is never sent to the wsa-replyTo EPR. Instead, the following message is sent:
<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header xmlns:wsa='http://www.w3.org/2005/08/addressing'><wsa:To>http://localhost:8080/WSAddressingServlet/wsaddressing</wsa:To><wsa:Action>http://soa.jboss.org/asynch/ncbi-blast-wsaOpResp</wsa:Action><wsa:RelatesTo>My-MessageID-2012</wsa:RelatesTo></env:Header><env:Body></env:Body></env:Envelope>
how can I sent the message generated at step 3 to the EPR referenced in the wsa-ReplyTo header?
thanks in advance
As far as the ESB services are concerned it should be a RequestResponse mep as you are expecting to send a response via the ebws endpoint. The WS-A behaviour should be handled independently by the SOAP stack, not directly by ESB, so it would appear to be something in that area that is causing you problems.
Can you attach an example showing the issue? We can then investigate further.