Project:
| View Revisions: Issue #32375 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0032375: preferences incorrectly resolve client visibility | ||
| Revision | 2016-03-04 08:32 by alostale | ||
| Description | Having the same preference with two records defined as: 1. visible at System client 2. visible at specific client Behavior when retrieving the value for this property is undefined: 1. Sometimes it can correctly return client specific value, which is the expected behavior 2. Some other times a PropertyConflictException is thrown |
||
| Revision | 2016-02-29 14:17 by ngarcia | ||
| Description | isHigherPriority function of Preferences class returns 0 when pref2 is defined as client level and pref1 as system level. The following condition should be checked the other way around and return 2: if ((pref2.getVisibleAtClient() == null || pref2.getVisibleAtClient().getId().equals("0")) && pref1.getVisibleAtClient() != null && !pref1.getVisibleAtClient().getId().equals("0")) { return 1; } As the getPreferences() function does not order the results |
||
| Revision | 2016-02-29 14:12 by ngarcia | ||
| Description | isHigerPriority function of Preferences class returns 0 when pref2 is defined as client level and pref1 as system level. The following condition should be checked the other way around and return 2: if ((pref2.getVisibleAtClient() == null || pref2.getVisibleAtClient().getId().equals("0")) && pref1.getVisibleAtClient() != null && !pref1.getVisibleAtClient().getId().equals("0")) { return 1; } As the getPreferences() function does not order the results |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |