cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Miłosz Pigłas (JIRA) <>
Subject [jira] [Commented] (CAY-1866) Change in General Modeler Preferences reverts old settings to default value
Date Tue, 27 Aug 2013 06:21:55 GMT


Miłosz Pigłas commented on CAY-1866:

In this case solution might be using unique identifier in method getPreferenceNode. For example
if we make call "Application.getInstance().getPreferenceNode(ClasspathPreferences.class, ClasspathPreferences.class.getSimpleName())"
classpath settings will be saved in node  /org/apache/cayenne/modeler/dialog/ClasspathPreferences/.
On the other hand in such scenario settings put in old version of modeler (compiled before
change) will be probably lost in new one.
> Change in General Modeler Preferences reverts old settings to default value
> ---------------------------------------------------------------------------
>                 Key: CAY-1866
>                 URL:
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Modeler
>    Affects Versions: 3.1B2, 3.2M1
>         Environment: Linux/Debian jdk 1.7
>            Reporter: Miłosz Pigłas
>            Priority: Minor
>             Fix For: 3.1B3, 3.2M2
>         Attachments: 1866.patch
> How to reproduce
> Cayenne Modeler
> 1. Tools->Preferences
> 2. Check "Automatically load last opened project"
> 3. Click 'Save'
> 4. Tools->Preferences
> 5. Check 'Always delete items without prompt'
> 6. Click 'Save'
> 7 Tools->Preferences: checkbox 'Automatically load last opened project' is unchecked;
'Always delete items ...'  is checked.
> ClasspathPreferences and GeneralPreferences store preferences in the same node.
> When user opens preferences editor and org.apache.cayenne.modeler.dialog.pref.ClasspathPreferences
is initalized keys for general preferences ('autoLoadProject, deletePrompt) are removed, because
they aren't integers and default values are set.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message