Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-bpmn2.dev] Question about BPMNPlanes

Hi Bob,
Sorry for the "too fast" answer. As far as I know there is no nesting of BPMNPlanes into BPMNShapes. BPMNShapes should be considered as leafs, except from labels and decorators.
There is also no good reason for such containment. You usually use Planes as visualization of Pools and Lanes. A Pool can contain Lanes, therefore a Plane can contain other plains. But a Shape, e.g. visualizing a Task could not contain a Plane.

Best regards,
 Reiner.


-----Original Message-----
From: mdt-bpmn2.dev-bounces@xxxxxxxxxxx [mailto:mdt-bpmn2.dev-bounces@xxxxxxxxxxx] On Behalf Of Bob Brodt
Sent: Mittwoch, 22. August 2012 16:25
To: BPMN2 Developers Mailing List
Subject: [mdt-bpmn2.dev] Question about BPMNPlanes

Hi all,

I'm not sure I understand the relationship of BPMNPlane elements to other DI model elements. It seems to me that you should be able to have containment of a BPMNPlane in a BPMNShape, something like this:

  <bpmndi:BPMNDiagram id="BPMNDiagram_1" name="Default Process Diagram">
    <bpmndi:BPMNPlane id="BPMNPlane_1" bpmnElement="process_1">
      <bpmndi:BPMNShape id="BPMNShape_1" bpmnElement="StartEvent_1">
        <dc:Bounds height="36.0" width="36.0" x="100.0" y="100.0"/>

        <bpmndi:BPMNPlane>
          <bpmndi:BPMNShape id="BPMNShape_2" bpmnElement="EndEvent_1">
            <dc:Bounds height="36.0" width="36.0" x="500.0" y="100.0"/>
          </bpmndi:BPMNShape>
         </bpmndi:BPMNPlane>
        
      </bpmndi:BPMNShape>
    </bpmndi:BPMNPlane>
  </bpmndi:BPMNDiagram>


When I try this, the XML parser tells me that "Feature 'BPMNPlane' not found." What am I missing here? Is this even allowed?

Thanks!
________________________
Robert ("Bob") Brodt
Senior Software Engineer
JBoss by Red Hat

_______________________________________________
mdt-bpmn2.dev mailing list
mdt-bpmn2.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev


Back to the top