Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 16 Oct 2013 14:09:42 +0000 (UTC)
From: "Kishan Kavala (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12662026.1375761576086.73373.1381932582415@arcas>
In-Reply-To: <JIRA.12662026.1375761576086@arcas>
References: <JIRA.12662026.1375761576086@arcas>
Subject: [jira] [Resolved] (CLOUDSTACK-4095) Region id within the Database
 Transaction code...
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kishan Kavala resolved CLOUDSTACK-4095.
---------------------------------------

    Resolution: Fixed

> Region id within the Database Transaction code...
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-4095
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4095
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Alex Huang
>            Assignee: Kishan Kavala
>            Priority: Critical
>             Fix For: 4.2.1
>
>
> Why should the region id be in Transaction Id and then propagated through GenericDao.  This is should not happen at all.  We need to fix this.  GenericDao is a generic framework.  It should not understand regions at all.  Even if you're using the db.properties to expose region id, you can read it yourself in your code, rather than pushing it into Transaction.


--
This message was sent by Atlassian JIRA
(v6.1#6144)