[
https://issues.apache.org/jira/browse/ODE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Yu updated ODE-579:
------------------------
Fix Version/s: 2.0
(was: 1.3.5)
Affects Version/s: 2.0-beta2
(was: 2.0)
> 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-beta2
> Environment: all
> Reporter: Andrey Kopachevsky
> Assignee: Matthieu Riou
> Fix For: 2.0
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
