[
https://issues.apache.org/jira/browse/ODE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafal Rusin updated ODE-588:
----------------------------
Attachment: onevent-scope-variable-fix.diff
It looks like this simple patch resolves problem:
Index: bpel-runtime/src/main/java/org/apache/ode/bpel/runtime/EH_EVENT.java
===================================================================
--- bpel-runtime/src/main/java/org/apache/ode/bpel/runtime/EH_EVENT.java
(revision 760397)
+++ bpel-runtime/src/main/java/org/apache/ode/bpel/runtime/EH_EVENT.java
(working copy)
@@ -292,7 +292,7 @@
// load 'onMessage' activity; we'll do this even
if a stop/terminate has been
// requested becasue we cannot undo the receipt of
the message at this point.
ActivityInfo child = new
ActivityInfo(genMonotonic(),
- _oevent.activity,
+ _oevent,
newChannel(TerminationChannel.class),
newChannel(ParentScopeChannel.class));
It looks like scope inside event handler was instantiated by its internal
activity instead of the whole scope activity.
> Scope inside OnEvent doesn't register variables on runtime
> ----------------------------------------------------------
>
> Key: ODE-588
> URL: https://issues.apache.org/jira/browse/ODE-588
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.2
> Reporter: Rafal Rusin
> Fix For: 1.3.2
>
> Attachments: onevent-scope-variable-fix.diff,
> onevent-scope-variable-test.diff, onevent-scope-variable-workaround.diff
>
>
> I did a construct like this:
> <scope>
> <onevent operation="...">
> <scope>
> <variables>
> ...
> </variables>
> <assign>...</assign>
> </scope>
> </onevent>
> </scope>
> When ODE enters assign activity, which contains a reference to variable
> declared in scope, there is a NPE and job fails.
> Surrounding scope with another scope is a workaround for this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
