Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 421431

Summary:	Sometimes no refresh in properties view
Product:	[Technology] Jubula	Reporter:	Sebastian Struckmann <sebastian.jubula>
Component:	UI	Assignee:	Marvin Mueller <marvin_m>
Status:	CLOSED FIXED	QA Contact:	Oliver Goetz <Oliver.Goetz>
Severity:	critical
Priority:	P2	CC:	Achim.Loerke, alexandra.schladebeck, katrin.hofmann, markus.tiede, marvin_m
Version:	unspecified	Keywords:	triaged
Target Milestone:	2.3
Hardware:	PC
OS:	All
Whiteboard:

Description Sebastian Struckmann

2013-11-11 05:10:08 EST

In some situations it happens that the properties view is not correctly refreshed.
One example for this is the behavior described in bug 421229.

But it can also be reproduced more general:
1. Open a node (e.g. a test suite) in the editor.
2. Change the name of this node via F2 from the test suite browser.
3. In the properties view the old name is still displayed.
4. Editing a comment does neither invokes a refreshing of the name nor does it affect what is displayed at "Recent Changes". It is necessary to close the editor and reopen it or to switch focus inside it to make the changes visible in the properties view.

Comment 1 Sebastian Struckmann

2013-11-11 05:14:50 EST

*** Bug 421229 has been marked as a duplicate of this bug. ***

Comment 2 Alexandra Schladebeck

2013-11-19 06:38:41 EST

*** Bug 378235 has been marked as a duplicate of this bug. ***

Comment 3 Alexandra Schladebeck

2013-12-02 08:22:34 EST

In addition to (or as a further example of) the behaviour described by Sebastian, it would appear that the properties view is somehow not the "correct" view. 

1. Follow steps 1-3 in the original comment.
2. Then rename the test suite via the editor in the properties view and save.
3. Even though the text can be entered and the editor can be saved, the information is not saved. This happens with data as well, and reminds me very much of the issue we have with saving editors (bug 389264).

This has nothing to do with the EclipseLink change. It was happening before the switch.

Comment 4 Marvin Mueller

2014-01-16 04:35:43 EST

We are now using the selection service for the properties page. I adapted the use of the selection provider for the Test Case Editor since this leads to some issues.

Fixed with changeset: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=421500c36cf74b1317caac87ddb2205d9e3e7584

Comment 5 Markus Tiede

2014-01-17 07:40:42 EST

I am no longer able to reproduce this issue.