On Mon, Jun 22, 2009 at 4:10 AM, Dietmar Wolz <[email protected]>wrote:
> Hallo, > the Eclipse Swordfish SOA Runtime Framework Project > http://www.eclipse.org/swordfish/ > uses Apache ODE as its process orchestration engine, > using the Eclipse Link based ODE database integration layer > from the Eclipse project SMILA http://www.eclipse.org/smila/ > > Different from Smila Swordfish uses the JBI IL of ODE inside Servicemix 4. > During integration we discovered a serious bug in the ODE 2.0 JBI IL and > filed it in JIRA: > > https://issues.apache.org/jira/browse/ODE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715082#action_12715082 > > In ODE 2.0 in the JBI IL > in org.apache.ode.jbi.OdeConsumer there is > > private void outResponse(final InOut jbiMex) { > PartnerRoleMessageExchange pmex = (PartnerRoleMessageExchange) > _ode._server.getMessageExchangeByForeignKey(jbiMex.getExchangeId()); > > the method getMessageExchangeByForeignKey is called which unfortunately > isn't > implemented yet. > > In ODE 1.2 we had in org.apache.ode.jbi.OdeConsumer > > private void outResponse(final InOut jbiMex) { > final PartnerRoleMessageExchange outstanding = > _outstandingExchanges.remove(jbiMex.getExchangeId()); > ... > public Boolean call() throws Exception { > PartnerRoleMessageExchange pmex = > (PartnerRoleMessageExchange) > _ode._server.getEngine().getMessageExchange(outstanding.getMessageExchangeId()); > > which worked. So there seems to be a refactoring from 1.2 to 2.0 which > wasn't completed correctly. > > Since the JBI IL is of crucial importance for us and we are bound to use > ODE 2.0 > because of IP compliance issues already solved by Eclipse SMILA for ODE 2.0 > beta, > we offer to fix the bug ourself (and contribute the patch to ODE). Could we > get > some hints/support from the ODE dev team? I'm having a look, I'll reply on the ticket once I have a fix. Matthieu > > Or is the fix already scheduled for ODE 2.0? > > Best Regards, Dr. Dietmar Wolz >
