Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Subject: Re: Hibernate
References: <F1DC278E-F69A-4409-A1FA-EFB80536B922@gnsa.us>
 <D52B60F166CBB4419763A924815F848A012D080C10FF@SJCPMAILBOX01.citrite.net>
From: David Nalley <david@gnsa.us>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: 
 <D52B60F166CBB4419763A924815F848A012D080C10FF@SJCPMAILBOX01.citrite.net>
Message-Id: <96B93665-BBD7-41C3-A1B0-A05ED1E57311@gnsa.us>
Date: Thu, 28 Jun 2012 00:51:27 -0400
To: "cloudstack-dev@incubator.apache.org"
 <cloudstack-dev@incubator.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)


On Jun 28, 2012, at 12:45 AM, Sheng Liang <Sheng.Liang@citrix.com> wrote:

>> In short, I see three options (please comment if you see more) 1. Rip out=
 hibernate and replace with some other ORM 2. Make the AWS API bits an optio=
nal non-default part of the build.
> 3. Declare that hibernate is a system requirement for CloudStack
>=20
> I prefer option #1. It is the cleanest. I don't think it will be very diff=
icult to rip out Hibernate.
>=20
> Sheng


That is my personal inclination as well, though I am somewhat reticent to sa=
y so, since I am not doing any of the work to rip and replace. At the same t=
ime choice of ORM is a big issue. I know, for instance that Alex was looking=
 into finding another ORM for the rest of CloudStack. When I initially looke=
d at the Hibernate issue, Prachi told me she thought it was about 2 weeks wo=
rth of work.


--David=