[jboss-jira] [JBoss JIRA] Closed: (JBRULES-1966) Editing existing ruleflow Action node not detected as a file change in eclipse plugin

[Mark Proctor (JIRA)]

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

Mark Proctor closed JBRULES-1966.
---------------------------------

    Fix Version/s: 5.0.0.FINAL
                       (was: 5.0.1.FINAL)
       Resolution: Done


> Editing existing ruleflow Action node not detected as a file change in eclipse plugin
> -------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1966
>                 URL: https://jira.jboss.org/jira/browse/JBRULES-1966
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-eclipse, drools-eclipse (expert), drools-eclipse (flow)
>    Affects Versions: 5.0.0.M5
>         Environment: Windows XP SP3, Sun JRE 1.5
>            Reporter: Shahad Ahmed
>            Assignee: Kris Verlaenen
>             Fix For: 5.0.0.FINAL
>
>
> I've found the following bug in the Ruleflow editor within the drools 5.0M5 eclipse plugin.
> If you edit an already existing action in an Action node of a ruleflow file then the edit is not detected as a change and the ruleflow file is not marked as dirty (i.e. no asterisk appears beside the ruleflow file name in it's editor tab). The change is shown in the properties tab, but is not saved to file, so that if you close the file then the change is not saved.
> The same problem occurs if you edit an existing "On Entry Actions" or "On Exit Actions" property in the following node types: Event Wait, Human Task, Email, Log 
> To reproduce:
> 1. Create a new ruleflow file consisting of a Start, Action and End node all connected together - do not save the file just yet.
> 2. Edit the Action node and add the following action: System.out.println("Hello");
> 3. Close the Action editor by clicking ok and save the ruleflow file.
> 4. Now open the Action node editor and edit the action to System.out.println("Hello World"); then click ok to close the Action editor.
> 5. At this point the change shows up against the Action property in the eclipse properties tab, but the Ruleflow editor tab does not show the file as changed. If you close the file now and reopen it then the changes to the Action are lost and the Action will still be System.out.println("Hello");
> A workaround is to move a node in the ruleflow after an edit to make the Ruleflow file dirty and then save it.

-- 
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