[jira] [Updated] (CAY-2599) Modeler: project becomes dirty when I switch to "DB Import" tab for the first time

["Andrus Adamchik (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAY-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrus Adamchik updated CAY-2599:
---------------------------------
    Description: 
This is a minor issue with Modeler design.. When you go to "DataMap > DB Import" tab for the first time for a given project, the project becomes dirty. This happens because <dbImport/> config is added to the project behind the scenes. Once it is added and saved, going to "DB Import" tab no longer dirties the project unless you actually make some changes.

Perhaps we should make it more explicit by adding some kind of "enable" button to this panel. Anyways, this is minor and we don't need to sweat it for 4.1

  was:
I have a Modeler build from the latest 4.1 branch. Steps:

* Open an existing project (initially in saved state)
* Click "DataMap > DB Import"

Outcome: Clicking "DB Import" changes the project state to dirty. 
Expected: Project should stay in the "saved" state

Not sure if this is related to CAY-2596 or not, but my build already includes CAY-2596 code.

        Summary: Modeler: project becomes dirty when I switch to "DB Import" tab for the first time  (was: Modeler: project becomes dirty when I switch to "DB Import" tab)

> Modeler: project becomes dirty when I switch to "DB Import" tab for the first time
> ----------------------------------------------------------------------------------
>
>                 Key: CAY-2599
>                 URL: https://issues.apache.org/jira/browse/CAY-2599
>             Project: Cayenne
>          Issue Type: Improvement
>    Affects Versions: 4.1.B2, 4.1.B3
>            Reporter: Andrus Adamchik
>            Assignee: Arseni Bulatski
>            Priority: Minor
>
> This is a minor issue with Modeler design.. When you go to "DataMap > DB Import" tab for the first time for a given project, the project becomes dirty. This happens because <dbImport/> config is added to the project behind the scenes. Once it is added and saved, going to "DB Import" tab no longer dirties the project unless you actually make some changes.
> Perhaps we should make it more explicit by adding some kind of "enable" button to this panel. Anyways, this is minor and we don't need to sweat it for 4.1



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)