[
https://jira.jboss.org/jira/browse/JBIDE-6248?page=com.atlassian.jira.plu...
]
Vlado Pakan commented on JBIDE-6248:
------------------------------------
I think it's not good to allow user to modify file and do not allow to save changes
after he has done his modification. Just imagine that user is doing changes for 1 hour and
when he wants to save them he find out that it's not allowed because file is
read-only. This is wrong.
Either JBT should display warning dialog informing that file is read-only and it's not
possible to modify it when the user starts modification of the file or don't allow any
modification to read-only files.
See my comment on
https://jira.jboss.org/jira/browse/JBIDE-6245
.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: Denny Xu
.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