You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Rafal Rusin (JIRA)" <ji...@apache.org> on 2009/03/18 23:21:50 UTC
[jira] Updated: (ODE-556) Rejecting in-out operations immediately
when there's no route found
[ https://issues.apache.org/jira/browse/ODE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin updated ODE-556:
----------------------------
Attachment: handleInOutInstantly.diff
handleInOutInstantly-soapui-project.xml
handleInOutInstantly.zip
I did a soap ui test case and a patch, which works for jbi version.
A patch works like this: when there's no route found, bpel runtime returns mex failure.
On Axis I get timeout, but it's probably just because of related issue https://issues.apache.org/jira/browse/ODE-555
> Rejecting in-out operations immediately when there's no route found
> -------------------------------------------------------------------
>
> Key: ODE-556
> URL: https://issues.apache.org/jira/browse/ODE-556
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Runtime
> Affects Versions: 1.3.1
> Reporter: Rafal Rusin
> Fix For: 1.3.1
>
> Attachments: handleInOutInstantly-soapui-project.xml, handleInOutInstantly.diff, handleInOutInstantly.zip
>
>
> A related discussion is here:
> http://markmail.org/thread/ethxp3y7373x72h3
> A goal is to implement handling in-out operations immediately - resulting in failure when there's no route registered.
> But in-only operation should queue messages for later dispatching (just like before).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.