[
http://jira.jboss.com/jira/browse/GPD-78?page=all ]
John Ruud updated GPD-78:
-------------------------
Description:
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.
was:
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.
Complexity: (was: Low)
I also had to make a similar change to HandlerDomAdapter.initialize(), for the same
reason
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.alpha4
Reporter: John Ruud
Assigned To: Koen Aers
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