[JBoss JIRA] Created: (JBPM-2084) Changing variable to null in subprocess doesn't change variable in superprocess, even when acces is "WRITE"
6:14 a.m.
Changing variable to null in subprocess doesn't change variable in superprocess, even
when acces is "WRITE"
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2084
URL: https://jira.jboss.org/jira/browse/JBPM-2084
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 3.2.x
Environment: windows XP/ java1.6/jboss 4.2.3GA/jbpm 3.2.7-SNAPSHOT from jboss
svn
Reporter: s p
Superprocess A sets variable V to value "foo".
Superprocess A calls subprocess B (A passes variable V to B with acces READ and WRITE).
Subprocess B sets variable V to #{null}.
Subprocess B finishes.
Superprocess checks value of V - it is equal "foo".
Expected behaviour:
value of V equal #{null} in superprocess A after execution of subprocess B.
This is becouse in ProcessState.java in methods execute and leave there is check:
if (value!=null) {
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:17 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2084) Changing variable to null in subprocess doesn't change variable in superprocess, even when acces is "WRITE"
[
https://jira.jboss.org/jira/browse/JBPM-2084?page=com.atlassian.jira.plug...
]
s p updated JBPM-2084:
----------------------
JBoss Forum Reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=73339
Description:
Superprocess A sets variable V to value "foo".
Superprocess A calls subprocess B (A passes variable V to B with acces READ and WRITE).
Subprocess B sets variable V to #{null}.
Subprocess B finishes.
Superprocess checks value of V - it is equal "foo".
Expected behaviour:
value of V equal #{null} in superprocess A after execution of subprocess B.
This is becouse in ProcessState.java in methods execute and leave there is check:
if (value!=null) {
//pass variable etc etc ..
This check can be removed and jbpm behaves as it should (I've checked in version 3.2.7
from svn).
But - I've found this thread -
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=73339 - it says this
check is to not throw NullPointer exception when process has out variable that it
doesn't write to it.
I've checked this situation with fixed version, and it don't throw exceptions, but
maybe I'm missing something.
was:
Superprocess A sets variable V to value "foo".
Superprocess A calls subprocess B (A passes variable V to B with acces READ and WRITE).
Subprocess B sets variable V to #{null}.
Subprocess B finishes.
Superprocess checks value of V - it is equal "foo".
Expected behaviour:
value of V equal #{null} in superprocess A after execution of subprocess B.
This is becouse in ProcessState.java in methods execute and leave there is check:
if (value!=null) {
Complexity: Low
Labels: jbpm variable process subprocess null pass (was: //pass
variable etc etc)
Changing variable to null in subprocess doesn't change variable
in superprocess, even when acces is "WRITE"
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2084
URL: https://jira.jboss.org/jira/browse/JBPM-2084
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 3.2.x
Environment: windows XP/ java1.6/jboss 4.2.3GA/jbpm 3.2.7-SNAPSHOT from jboss
svn
Reporter: s p
Superprocess A sets variable V to value "foo".
Superprocess A calls subprocess B (A passes variable V to B with acces READ and WRITE).
Subprocess B sets variable V to #{null}.
Subprocess B finishes.
Superprocess checks value of V - it is equal "foo".
Expected behaviour:
value of V equal #{null} in superprocess A after execution of subprocess B.
This is becouse in ProcessState.java in methods execute and leave there is check:
if (value!=null) {
//pass variable etc etc ..
This check can be removed and jbpm behaves as it should (I've checked in version
3.2.7 from svn).
But - I've found this thread -
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=73339 - it says this
check is to not throw NullPointer exception when process has out variable that it
doesn't write to it.
I've checked this situation with fixed version, and it don't throw exceptions,
but maybe I'm missing something.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:30 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2084) Changing variable to null in subprocess doesn't change variable in superprocess, even when acces is "WRITE"
[
https://jira.jboss.org/jira/browse/JBPM-2084?page=com.atlassian.jira.plug...
]
s p updated JBPM-2084:
----------------------
Attachment: ProcessState.patch
Proposed patch
Changing variable to null in subprocess doesn't change variable
in superprocess, even when acces is "WRITE"
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2084
URL: https://jira.jboss.org/jira/browse/JBPM-2084
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 3.2.x
Environment: windows XP/ java1.6/jboss 4.2.3GA/jbpm 3.2.7-SNAPSHOT from jboss
svn
Reporter: s p
Attachments: ProcessState.patch
Superprocess A sets variable V to value "foo".
Superprocess A calls subprocess B (A passes variable V to B with acces READ and WRITE).
Subprocess B sets variable V to #{null}.
Subprocess B finishes.
Superprocess checks value of V - it is equal "foo".
Expected behaviour:
value of V equal #{null} in superprocess A after execution of subprocess B.
This is becouse in ProcessState.java in methods execute and leave there is check:
if (value!=null) {
//pass variable etc etc ..
This check can be removed and jbpm behaves as it should (I've checked in version
3.2.7 from svn).
But - I've found this thread -
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=73339 - it says this
check is to not throw NullPointer exception when process has out variable that it
doesn't write to it.
I've checked this situation with fixed version, and it don't throw exceptions,
but maybe I'm missing something.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:40 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-2084) Changing variable to null in subprocess doesn't change variable in superprocess, even when acces is "WRITE"
[
https://issues.jboss.org/browse/JBPM-2084?page=com.atlassian.jira.plugin....
]
Alejandro Guizar updated JBPM-2084:
-----------------------------------
Assignee: Alejandro Guizar
Fix Version/s: jBPM 3.2.x
Affects Version/s: jBPM 3.2.7
(was: jBPM 3.2.x)
Description:
Superprocess A sets variable V to value "foo".
Superprocess A calls subprocess B (A passes variable V to B with acces READ and WRITE).
Subprocess B sets variable V to #{null}.
Subprocess B finishes.
Superprocess checks value of V - it is equal "foo".
Expected behaviour:
value of V equal #{null} in superprocess A after execution of subprocess B.
This is becouse in ProcessState.java in methods execute and leave there is check:
if (value!=null) {
//pass variable etc etc ..
This check can be removed and jbpm behaves as it should (I've checked in version 3.2.7
from svn).
But - I've found this thread -
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=73339 - it says this
check is to not throw NullPointer exception when process has out variable that it
doesn't write to it.
I've checked this situation with fixed version, and it don't throw exceptions, but
maybe I'm missing something.
was:
Superprocess A sets variable V to value "foo".
Superprocess A calls subprocess B (A passes variable V to B with acces READ and WRITE).
Subprocess B sets variable V to #{null}.
Subprocess B finishes.
Superprocess checks value of V - it is equal "foo".
Expected behaviour:
value of V equal #{null} in superprocess A after execution of subprocess B.
This is becouse in ProcessState.java in methods execute and leave there is check:
if (value!=null) {
//pass variable etc etc ..
This check can be removed and jbpm behaves as it should (I've checked in version 3.2.7
from svn).
But - I've found this thread -
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=73339 - it says this
check is to not throw NullPointer exception when process has out variable that it
doesn't write to it.
I've checked this situation with fixed version, and it don't throw exceptions, but
maybe I'm missing something.
To be reviewed and incorporated in a future jBPM version.
Changing variable to null in subprocess doesn't change variable
in superprocess, even when acces is "WRITE"
-----------------------------------------------------------------------------------------------------------
Key: JBPM-2084
URL: https://issues.jboss.org/browse/JBPM-2084
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 3.2.7
Environment: windows XP/ java1.6/jboss 4.2.3GA/jbpm 3.2.7-SNAPSHOT from jboss
svn
Reporter: s p
Assignee: Alejandro Guizar
Labels: jbpm, null, pass, process, subprocess, variable
Fix For: jBPM 3.2.x
Attachments: ProcessState.patch
Superprocess A sets variable V to value "foo".
Superprocess A calls subprocess B (A passes variable V to B with acces READ and WRITE).
Subprocess B sets variable V to #{null}.
Subprocess B finishes.
Superprocess checks value of V - it is equal "foo".
Expected behaviour:
value of V equal #{null} in superprocess A after execution of subprocess B.
This is becouse in ProcessState.java in methods execute and leave there is check:
if (value!=null) {
//pass variable etc etc ..
This check can be removed and jbpm behaves as it should (I've checked in version
3.2.7 from svn).
But - I've found this thread -
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=73339 - it says this
check is to not throw NullPointer exception when process has out variable that it
doesn't write to it.
I've checked this situation with fixed version, and it don't throw exceptions,
but maybe I'm missing something.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5130
days inactive
5775
days old
3 comments
2 participants
participants (2)
-
Alejandro Guizar (JIRA) -
s p (JIRA)