Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370211 - ItemDefinition kind field defaults to physical, instead of information
Summary: ItemDefinition kind field defaults to physical, instead of information
Status: RESOLVED FIXED
Alias: None
Product: BPMN2Modeler
Classification: SOA
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 0.0.1-M1   Edit
Assignee: Robert Brodt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-31 07:55 EST by Gary Brown CLA
Modified: 2012-03-20 15:03 EDT (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 Gary Brown CLA 2012-01-31 07:55:47 EST 
Build Identifier: 

According to the BPMN2 spec, the default for the kind field should be information.

Not sure if this is a BPMN2 EMF model issue, or a mistake in the XSD schema from which it was derived.

Reproducible: Always
Comment 1 Robert Brodt CLA 2012-03-01 10:16:59 EST 
Yep, the eclipse bpmn2 metadata project does have Physical as the default. This needs to be fixed in that project.

Created https://bugs.eclipse.org/bugs/show_bug.cgi?id=372981 to track this.
Comment 2 Robert Brodt CLA 2012-03-20 15:03:20 EDT 
This was fixed in the bpmn2 metamodel project.