[ https://issues.apache.org/jira/browse/ODE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou updated ODE-579: ------------------------------ Attachment: mex-by-fk-patch.txt Here is a patch for your issue. I'm unable to test it easily so could you give it a try? The patch has been produced with git so to apply: patch -p1 < path/to/patch/file > Ode 2.0 beta problem while using pathner service - corresponding method not > implemented > --------------------------------------------------------------------------------------- > > Key: ODE-579 > URL: https://issues.apache.org/jira/browse/ODE-579 > Project: ODE > Issue Type: Bug > Components: BPEL Runtime > Affects Versions: 2.0 > Environment: all > Reporter: Andrey Kopachevsky > Attachments: mex-by-fk-patch.txt > > > We (Eclipse Swordfish project team) are using ODE with apache ServiceMix 4. > Our test example consists of > simple bpel process that invoke jax-ws web service during execution and > return result. > Ode 1.2 works fine with that. But ODE 2.0 beta not returns any response to > caller. And I see following warning in logs: > *WARNING: Received a response for unknown partner role message exchange > 11ee7ee0-28f9-4250-9c6c-e9becf573f7f* > After research source codes we find following code snippet inside > org.apache.ode.jbi.OdeConsumer: > private void outResponse(final InOut jbiMex) { > PartnerRoleMessageExchange pmex = (PartnerRoleMessageExchange) > > _ode._server.getMessageExchangeByForeignKey(jbiMex.getExchangeId()); > if (pmex == null) { > __log.warn("Received a response for unknown partner > role message exchange " + jbiMex.getExchangeId()); > return; > } > ........... > so _ode._server.getMessageExchangeByForeignKey(jbiMex.getExchangeId() retutns > NULL; > I've check _ode._server implementation class with is BpelServerImpl and find > out that getMessageExchangeByForeignKey method not implemented: > public MessageExchange getMessageExchangeByForeignKey(String foreignKey) > throws BpelEngineException { > // TODO Auto-generated method stub > return null; > } > It is very big issue for us, -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.