Bug 780154 (SOA-2529) - NPE when trying to add an activity to onAlarm branch in pick.
Summary: NPE when trying to add an activity to onAlarm branch in pick.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2529
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: BPEL editor
Version: 5.1.0.ER3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0 GA
Assignee: Brian Fitzpatrick
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-02 10:30 UTC by Marek Baluch
Modified: 2011-02-10 23:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-10 23:50:39 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2529 0 None None None Never

Description Marek Baluch 2010-11-02 10:30:06 UTC 
project_key: SOA

See linked issue.
Comment 1 Marek Baluch 2010-11-02 10:30:24 UTC 
Link: Added: This issue depends JBIDE-7480
Comment 2 Anne-Louise Tangring 2010-11-09 15:47:58 UTC 
Candidate for SOA 5.1.0
Comment 3 Brian Fitzpatrick 2010-11-09 16:21:09 UTC 
This has been fixed in JBDS for the 4.0.0.beta2 release.
Comment 4 Marek Baluch 2010-11-29 14:45:45 UTC 
Verified on JBoss Tools 3.2 Beta 2
- BPEL editor version 1.0.0.v20101122-2055-H270-Beta2
Comment 5 David Le Sage 2011-02-10 23:47:43 UTC 
Temporarily reopening issue to add release note info.
Comment 6 David Le Sage 2011-02-10 23:50:29 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/JBIDE-7480

A null-pointer exception occurred when the user added an activity to an onAlarm scope. This was caused by a bug in ReconciliationHelper.java.  The code has been rectified and, as a result, the user can now add an activity to that scope without encountering an exception.
Note You need to log in before you can comment on or make changes to this bug.