[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-6248) .brl files from Guvnor examples are not properly read-only.

Vlado Pakan (JIRA) jira-events at lists.jboss.org
Mon May 3 09:41:06 EDT 2010


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

Vlado Pakan updated JBIDE-6248:
-------------------------------

    Description: 
.brl files from Guvnor Repository examples are opened as read-only but it's possible to modified them via .brl file editor in JBT.
It's even possible to save modified file and everything looks correctly saved. But when file is reopened there are no changes saved.
It should not be possible to edit read-only .brl file.

1. deploy guvnor to server and start server
2. open guvnor perspective
3. add default guvnor repository connection using Guvnor Repositories view
4. right click on newly created Guvnor connection and open Guvnor Console
5. choose ok to empty login dialog and click yes to install Guvnor examples
6. open <Guvnor connection> > pacakges > mortages > CheckBoxDslRule.brl file from Guvnor Repositories view
7. add new free form drl to condition save button gets enabled file looks like modified
8. save file everything looks like file is saved
9. Reopen the file and changes are not saved

  was:
.dsl files from Guvnor Repository examples are opened as read-only but it's possible to modified them via .dsl file editor in JBT.
When trying to save this read-only file JBT display this error:

Save Failed
org.guvnor.tools.utils.StringInput cannot be cast to org.eclipse.ui.part.FileEditorInput

It should not be possible to modify read-only .dsl file.

Steps to reproduce:

1. deploy guvnor to server and start server
2. open guvnor perspective
3. add default guvnor repository connection using Guvnor Repositories view
4. right click on newly created Guvnor connection and open Guvnor Console
5. choose ok to empty login dialog and click yes to install Guvnor examples
6. open <Guvnor connection> > pacakges > mortages > ApplicantDsl.dsl file from Guvnor Repositories view
7. select first expresion in opened ApplicantDsl.dsl file and click on edit button
8. click on OK button in Edit Language Mappiing dialog. It's not necessary to make any changes.
9. Choose save for ApplicantDsl.dsl file and error mentioned above is displayed



> .brl files from Guvnor examples are not properly read-only.
> -----------------------------------------------------------
>
>                 Key: JBIDE-6248
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-6248
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: drools
>    Affects Versions: 3.1.x
>         Environment: Fedora Linux v.11
> JBossTools-Update-3.1.0.v201004291720R-H72-GA
> Java 1.6Sun JDK
> JBoss EAP 5.0
>            Reporter: Vlado Pakan
>            Assignee: Kris Verlaenen
>
> .brl files from Guvnor Repository examples are opened as read-only but it's possible to modified them via .brl file editor in JBT.
> It's even possible to save modified file and everything looks correctly saved. But when file is reopened there are no changes saved.
> It should not be possible to edit read-only .brl file.
> 1. deploy guvnor to server and start server
> 2. open guvnor perspective
> 3. add default guvnor repository connection using Guvnor Repositories view
> 4. right click on newly created Guvnor connection and open Guvnor Console
> 5. choose ok to empty login dialog and click yes to install Guvnor examples
> 6. open <Guvnor connection> > pacakges > mortages > CheckBoxDslRule.brl file from Guvnor Repositories view
> 7. add new free form drl to condition save button gets enabled file looks like modified
> 8. save file everything looks like file is saved
> 9. Reopen the file and changes are not saved

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