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 22:55:50 UTC
[jira] Created: (ODE-556) Rejecting in-out operations immediately
when there's no route found
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
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.
[jira] Assigned: (ODE-556) Rejecting in-out operations immediately
when there's no route found
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin reassigned ODE-556:
-------------------------------
Assignee: Rafal Rusin
> 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.2
> Reporter: Rafal Rusin
> Assignee: Rafal Rusin
> Fix For: 1.3.5
>
> 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.
-
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
[jira] Commented: (ODE-556) Rejecting in-out operations immediately
when there's no route found
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888608#action_12888608 ]
Hudson commented on ODE-556:
----------------------------
Integrated in ODE-trunk #337 (See [http://hudson.zones.apache.org/hudson/job/ODE-trunk/337/])
> 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.2
> Reporter: Rafal Rusin
> Assignee: Rafal Rusin
> Fix For: 1.3.5
>
> 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.
[jira] Updated: (ODE-556) Rejecting in-out operations immediately
when there's no route found
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated ODE-556:
---------------------------------
Fix Version/s: 1.3.5
(was: 1.3.4)
Postponed to 1.3.5.
> 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.2
> Reporter: Rafal Rusin
> Assignee: Rafal Rusin
> Fix For: 1.3.5
>
> 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.
-
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
[jira] Updated: (ODE-556) Rejecting in-out operations immediately
when there's no route found
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert updated ODE-556:
------------------------------
Fix Version/s: (was: 1.3.3)
1.3.4
> 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.2
> Reporter: Rafal Rusin
> Fix For: 1.3.4
>
> 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.
[jira] Resolved: (ODE-556) Rejecting in-out operations immediately
when there's no route found
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin resolved ODE-556.
-----------------------------
Resolution: Fixed
I implemented global switch org.apache.ode.queueInOutMessages, true by default.
If set to false, ODE will reject immediately in-out operations once no routing was found.
> 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.2
> Reporter: Rafal Rusin
> Assignee: Rafal Rusin
> Fix For: 1.3.5
>
> 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.
[jira] Updated: (ODE-556) Rejecting in-out operations immediately
when there's no route found
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon updated ODE-556:
-----------------------------
Fix Version/s: (was: 1.3.1)
1.3.2
> 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.2
>
> 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.
[jira] Updated: (ODE-556) Rejecting in-out operations immediately
when there's no route found
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ 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.