| Summary: | ItemDefinition.structureRef property not being handled correctly | ||
|---|---|---|---|
| Product: | [SOA] BPMN2Modeler | Reporter: | Robert Brodt <bbrodt> |
| Component: | UI | Assignee: | Robert Brodt <bbrodt> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | reiner.hille-doering |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| URL: | https://issues.jboss.org/browse/JBPM-3173 | ||
| Whiteboard: | |||
|
Description
Robert Brodt
I'm still convinced that a reference to EObject is correct. In the XSD model of BPMN2 it is a QName, which is a clear sign that they expect a kind of valid reference to something (whatever something means). It could be a reference to an XSD complex type or Element. But it could also be a reference to any proprietary Data structure containing any kind of information. For the EMF model it means that it could point to an EObject from a private class, e.g. containing some strings. We had a similar discussion on the list some time ago. See here: http://dev.eclipse.org/mhonarc/lists/mdt-bpmn2.dev/msg00151.html There is even an example, how you could but a string into the structureRef property using the EOject proxyURI. Fixed. |