Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355654 - Issue with escalation (id not found)
Summary: Issue with escalation (id not found)
Status: RESOLVED FIXED
Alias: None
Product: BPMN2Modeler
Classification: SOA
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Robert Brodt CLA
QA Contact:
URL: https://issues.jboss.org/browse/JBPM-...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-24 06:24 EDT by Robert Brodt CLA
Modified: 2011-12-05 12:44 EST (History)
0 users

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Brodt CLA 2011-08-24 06:24:44 EDT 
Brian Fitzpatrick added a comment - 06/Jul/11 2:31 PM

Anything more about this one? Repro steps? Samples? Clues?
Robert (Bob) Brodt added a comment - 13/Jul/11 3:58 PM

Hmmm...good question. I think this came out of a discussion I had with Kris but I'm not sure about the details. Kris, can you elaborate?
Robert (Bob) Brodt added a comment - 13/Jul/11 3:59 PM

Any details about this one?
Kris Verlaenen added a comment - 13/Jul/11 5:08 PM

I get the error "FeatureNotFoundException: Feature 'id' not found." when opening processes that contain escalation nodes, like for example:
https://github.com/droolsjbpm/jbpm/blob/master/jbpm-examples/src/main/resources/junit/BPMN2-EscalationBoundaryEventInterrupting.bpmn2
Seems to be a problem with the metamodel, not accepting id as a valid property of escalation.
Comment 1 Robert Brodt CLA 2011-12-05 12:44:31 EST 
Fixed