Bug 724384 (BRMS-330) - Editing in Multiple Tabs and State Management
Summary: Editing in Multiple Tabs and State Management
Keywords:
Status: VERIFIED
Alias: BRMS-330
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: unspecified
Version: 5.0.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: future
Assignee: trev
QA Contact: Jiri Locker
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-09 15:27 UTC by Jim Tyrrell
Modified: 2020-04-27 01:30 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
All
Last Closed:
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-330 0 None Closed Editing in Multiple Tabs and State Management 2012-05-23 09:20:07 UTC

Description Jim Tyrrell 2010-06-09 15:27:26 UTC
securitylevel_name: Public

When I am editing in multiple tabs I am seeing odd behavior where one item does not always result in an updated item in the pane I am editing resulting in pain ;)

Open a DSL File
Open a Guided Rule Editor
Open a Test Case

If I make changes to the DSL file and click Save Changes
without closing and reopening the Guided Rule Editor I do not see the above DSL file changes
The test case can not be updated with the current items in the DSL or the Guided Rule Editor.

It appears that state management is going on under the covers, but I am not sure this is the right user interface as you have to have a super brain to keep track of all of these things that are moving around as you are making changes.

Comment 3 Jiri Locker 2012-05-23 09:20:00 UTC
Seems to be working:

* New DSL sentences are available in Guided editor
* Changes in model are available in Guided editor and test scenarios

Please be aware that saving declarative models, DSL configurations and enums will throw away any unsaved changes in assets in the same package. This is already reported as bug 758199.

This one is verified in ER7.


Note You need to log in before you can comment on or make changes to this bug.