[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-3490) dirty jBPM Graphical Process Designer editor saves layout changes without prompting user or loses changes if gpd.xml is open to Source tab

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Wed Aug 19 05:14:29 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBIDE-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-3490:
---------------------------------------

    Fix Version/s: 3.1.0.M4
                       (was: 3.1.0.M3)


moved because of no update.

> dirty jBPM Graphical Process Designer editor saves layout changes without prompting user or loses changes if gpd.xml is open to Source tab
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-3490
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3490
>             Project: JBoss Tools
>          Issue Type: Bug
>          Components: jbpm
>    Affects Versions: 3.0.0.cr1
>            Reporter: Nick Boldt
>            Assignee: Koen Aers
>             Fix For: 3.1.0.M4
>
>
> Tested with JBoss Dev Studio Version: 2.0.0.CR1, Build id: R200812221144
> Steps to repro:
> 1. Install JBDS.
> 2. download http://www.jboss.org/downloading/?projectId=jbossjbpm&url=http://downloads.sourceforge.net/jbpm/jbpm-installer-3.3.0.GA.jar
> 3. `java -jar jbpm-installer-3.3.0.GA.jar`. I installed into ~/jbpm-3.3.0.GA
> 4. New > Other > Process Project
> 5. Go into src/main/jpdl/simple and open processdefinition.xml with jBPM Graphical Process Designer
> 6. Add a couple nodes, then connect them to the existing flow.
> 7. Switch to Source tab. I had this:
> <?xml version="1.0" encoding="UTF-8"?>
> <process-definition
>   xmlns="urn:jbpm.org:jpdl-3.2"
>   name="simple">
>    <start-state name="start">
>       <transition name="to_state" to="first">
>          <action name="action" class="com.sample.action.MessageActionHandler">
>             <message>Going to the first state!</message>
>          </action>
>       </transition>
> <transition to="mail-node1" name="to mail-node1"></transition>
>    </start-state>
>    <state name="first">
>       <transition name="to_end" to="end">
>          <action name="action" class="com.sample.action.MessageActionHandler">
>             <message>About to finish!</message>
>          </action>
>       </transition>
>    </state>
> <task-node name="task-node1">
> <transition to="end"></transition>
> </task-node>
> <mail-node name="mail-node1">
> <transition to="task-node1"></transition>
> </mail-node>
>    <end-state name="end"></end-state>
> </process-definition> 
> 8. Click [x] on editor tab to close it. You should be prompted to save dirty editor. Save.
> 9. Reopen editor. Move some nodes around. Note editor is again in 'dirty' state.
> 10. Click [x] on editor tab to close it. This time you're not prompted to save (because the changes are in a different file, gpd.xml). 
> 11. Repeat steps 9-10, verifying that changes to layout are saved into gpd.xml.
> ** Surely these changes to UI layout shouldn't be automatically written without the user's confirmation? **
> --
> 11. Open gpd.xml using xml editor. Switch to Source tab and note (x,y) coords for the start node. 
> 12. Reopen processdefinition.xml in jBPM Graphical Process Designer editor. Move the start node. Note editor is again in 'dirty' state, as in step 9 above.
> 13. Click [x] on editor tab to close it. Still not prompted, as in step 10. Close gpd.xml too. 
> 14. Reopen gpd.xml. This time, nothing has changed!
> ** Surely layout changes shouldn't just vanish if the gpd.xml file's open in parallel with the jBPM Graphical Process Designer editor? **

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

        


More information about the jbosstools-issues mailing list