[jboss-jira] [JBoss JIRA] Updated: (GPD-78) configInfoElements of semantic elements are not always added to XML adapters

John Ruud (JIRA) jira-events at lists.jboss.org
Thu Aug 9 17:19:20 EDT 2007


     [ http://jira.jboss.com/jira/browse/GPD-78?page=all ]

John Ruud updated GPD-78:
-------------------------


Koen,

Here's some of my node samples (as you can see they're similar to Imran's in complexity):

   <nodeSign name="nodeSign1">
      <action class="com.xyz.ActionSign">
         <MyTag>
            <SignatureType></SignatureType>
         </MyTag>
      </action>
   </nodeSign>

   <decideIsTime name="decision3">
      <handler class="com.xyz.DecideIsTime">
         <MyTag>
            <CompareDate>
               <DateTime format="HH:mm" operator="between"></DateTime>
            </CompareDate>
         </MyTag>
      </handler>
   </decideIsTime>

   <state name="state1">
      <event type="node-enter">
         <action class="com.xyz.SetTask">
            <MyTag>
               <ProcessingTypeID></ProcessingTypeID>
            </MyTag>
         </action>
      </event>
      <event type="node-leave">
         <action class="com.xyz.SetTaskClear"></action>
      </event>
   </state>

> configInfoElements of semantic elements are not always added to XML adapters
> ----------------------------------------------------------------------------
>
>                 Key: GPD-78
>                 URL: http://jira.jboss.com/jira/browse/GPD-78
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: John Ruud
>         Assigned To: Koen Aers
>             Fix For: jBPM JPDL Designer 3.1.0.GA
>
>         Attachments: GPD-78.patch
>
>
> For example, if a node that contains an Action with a non-empty configInfoElements collection is added to the diagram, the configInfoElements collection is not assigned in the ActionDomAdapter. 
> I added the following line to the end of the "if (action != null)" clause in ActionDomAdapter.initialize(): 
> addElements(action.getConfigInfoElements()); 
> .. and then things seems to work. I believe this is similar to for example how the events collection is currently initialized in DecisionDomAdapter.initialize(), while of course there may be side effects that I'm not aware of. 
> It would be great if a fix (possibly the one described above) can be included in GD 3.1.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list