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

Bug 361569

Summary:

Using AlwaysIncludeSortAtBegin or AlwaysIncludeSortAtEnd flag on a column enforces setting the sortIndex to take effect on the sort order.

Product:

z_Archived

Reporter:

Oli Schmid <oliver.schmid>

Component:

Scout

Assignee:

Claudio Guglielmo <claudio.guglielmo>

Status:

CLOSED FIXED

QA Contact:

Severity:

minor

Priority:

CC:

claudio.guglielmo

Version:

unspecified

Flags:

claudio.guglielmo: juno+

Target Milestone:

---

Hardware:

OS:

Windows Vista

Whiteboard:

Attachments:

Description	Flags
Write a warning into the LOG when no index is defined.	claudio.guglielmo: iplog+

Description Oli Schmid

2011-10-20 11:38:42 EDT

Reproducible: Always

Steps to Reproduce:
1. Define a column on a table page with the flag AlwaysIncludeSortAtBegin  set to true.

2. Ensure the table is filled with data provided by a backend service.

3. Check if the data is really sorted by the defined column.

--> It will not as long as the sortIndex is not defined.

Suggestions: Write at least a warning to the log file when one of the flag is set but no index is defined.

Comment 1 Oli Schmid

2011-10-20 11:39:47 EDT

Created attachment 205647 [details]
Write a warning into the LOG when no index is defined.

Does the suggested work.

Comment 2 Claudio Guglielmo

2012-05-01 06:52:21 EDT

Thank you for the patch! It's applied as suggested.

Comment 3 Matthias Zimmermann

2012-07-09 06:50:13 EDT

ticket closed.
deliverd as part of eclipse scout 3.8.0 (juno release train)