Bug 816908
| Summary: | Bpm5Processor does not map BPM parameters on SIGNAL_EVENT. | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Marek Baluch <mbaluch> |
| Component: | JBossESB | Assignee: | tcunning |
| Status: | VERIFIED --- | QA Contact: | Marek Baluch <mbaluch> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.3.0 GA | CC: | soa-p-jira, tcunning |
| Target Milestone: | ER4 | ||
| Target Release: | 5.3.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.3.0 GA | Doc Type: | Bug Fix |
| Doc Text: |
Bpm5Processor does not map BPM parameters on SIGNAL_EVENT. This means that parameters added by users will be ignored. This is resolved by mapping the parameters and passing them in a signalEvent. As a result, user-defined parameters will now take affect.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Marek Baluch
2012-04-27 09:42:34 UTC
Tom Cunningham <tcunning> updated the status of jira JBESB-3792 to Resolved Tom Cunningham <tcunning> made a comment on jira JBESB-3792 Map parameters and pass them in a signalEvent. Tom Cunningham <tcunning> updated the status of jira JBESB-3792 to Closed bananastand:jbpm5 tcunning$ svn commit Sending jbpm5/src/main/java/org/jboss/soa/esb/services/jbpm5/actions/Bpm5Processor.java Transmitting file data . Committed revision 38120. bananastand:jbpm5 tcunning$
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Bpm5Processor does not map BPM parameters on SIGNAL_EVENT. This is resolved by mapping the parameters and passing them in a signalEvent.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-Bpm5Processor does not map BPM parameters on SIGNAL_EVENT. This is resolved by mapping the parameters and passing them in a signalEvent.+Bpm5Processor does not map BPM parameters on SIGNAL_EVENT. These means that parameters users add will be ignored. This is resolved by mapping the parameters and passing them in a signalEvent. As a result, user-defined parameters will now take affect.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-Bpm5Processor does not map BPM parameters on SIGNAL_EVENT. These means that parameters users add will be ignored. This is resolved by mapping the parameters and passing them in a signalEvent. As a result, user-defined parameters will now take affect.+Bpm5Processor does not map BPM parameters on SIGNAL_EVENT. This means that parameters added by users will be ignored. This is resolved by mapping the parameters and passing them in a signalEvent. As a result, user-defined parameters will now take affect.
Verified on 5.3 ER4. Parameters are now accessible in the process as an object of type java.util.Map and can processed inside a script task. |