.
--Alex
> -Original Message-
> From: Will Chan [mailto:will.c...@citrix.com]
> Sent: Wednesday, August 15, 2012 5:33 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate -> Custom DAO for AWS component
>
> I'm pretty sure you can because the Usage S
and 'cloud' db (used by EC2 to pull
> cloudstack configuration/service offering/default zone info) With hibernate
> we could do that.
>
> -Prachi
>
> -Original Message-
> From: Rajesh Battala [mailto:rajesh.batt...@citrix.com]
> Sent: Monday, August
ng/default zone info)
With hibernate we could do that.
-Prachi
-Original Message-
From: Rajesh Battala [mailto:rajesh.batt...@citrix.com]
Sent: Monday, August 13, 2012 10:46 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Hibernate -> Custom DAO for AWS component
I will r
> -Original Message-
> From: Darren Shepherd [mailto:dar...@godaddy.com]
> Sent: Monday, August 13, 2012 1:29 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate -> Custom DAO for AWS component
>
> I think there's two points.
>
> 1
@incubator.apache.org
Subject: RE: Hibernate -> Custom DAO for AWS component
I think there's two points.
1) Raw SQL is bad, so even in a time crunch moving to the custom CloudStack DAO
implementation *should* have been better.
2) I'd rather see a JPA based solution then moving to custom CloudStack
> -Original Message-
> From: Darren Shepherd [mailto:dar...@godaddy.com]
> Sent: Monday, August 13, 2012 1:29 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate -> Custom DAO for AWS component
>
>
> I think Alex and I agree on point 1,
sure if anybody agrees
with point 2. What's the time frame for when this was supposed to be
done?
Darren
Original Message ----
Subject: RE: Hibernate -> Custom DAO for AWS component
From: Will Chan
Date: Mon, August 13, 2012 12:56 pm
To: "cloudstack-dev@incubator.apa
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Monday, August 13, 2012 10:33 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate -> Custom DAO for AWS component
>
>
>
> > -Original Message-
>
> -Original Message-
> From: Darren Shepherd [mailto:dar...@godaddy.com]
> Sent: Sunday, August 12, 2012 8:25 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Hibernate -> Custom DAO for AWS component
>
> All,
>
> I was just reviewing https://reviews.apache.org/r/6557/diff/ for t
Battala
-Original Message-
From: David Nalley [mailto:da...@gnsa.us]
Sent: Thursday, August 09, 2012 8:43 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: Hibernate
Rajesh, is this done?
--David
On Mon, Jul 16, 2012 at 11:49 PM, Rajesh Battala
wrote:
> Yes Ewan, I would be do
sage-
> >> From: Ewan Mellor [mailto:ewan.mel...@eu.citrix.com]
> >> Sent: Tuesday, July 17, 2012 9:03 AM
> >> To: cloudstack-dev@incubator.apache.org
> >> Subject: RE: Hibernate
> >>
> >> OK, good. So it's a small job. So is Rajesh doing
sday, July 17, 2012 9:03 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: RE: Hibernate
>>
>> OK, good. So it's a small job. So is Rajesh doing that?
>>
>> Ewan.
>>
>> > -Original Message-
>> > From: Alex Huang [mailto
Yes Ewan, I would be doing this work.
Thanks
Rajesh Battala
> -Original Message-
> From: Ewan Mellor [mailto:ewan.mel...@eu.citrix.com]
> Sent: Tuesday, July 17, 2012 9:03 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate
>
> OK, good. So it&
OK, good. So it's a small job. So is Rajesh doing that?
Ewan.
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: 16 July 2012 17:03
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate
>
> My understanding is it&
PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate
>
> If I read this infinitely long thread correctly, the conclusion is that
> CloudStack/awsapi needs to be rewritten to use the CloudStack DAO instead
> of Hibernate. Is that correct?
>
> If so, who is do
age-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Monday, July 02, 2012 11:31 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate
>
> Rajesh,
>
> You should use the existing CloudStack DAO framework. If cloudstack
> will move to another ORM
> I don't want to speak for Alex, but I have heard him mention such a change
> number of times, and have seen it in his slides as well.
>
> But the larger sense is that if we are going to change something in AWSAPI
> for communicating to the database, it should be something that we are
> comfortab
Which would mean your code
should migrate over along with the rest of the changes.
--Alex
> -Original Message-
> From: Rajesh Battala [mailto:rajesh.batt...@citrix.com]
> Sent: Monday, July 02, 2012 10:59 PM
> To: cloudstack-dev@incubator.apache.org
> Su
> -Original Message-
> From: Kelven Yang [mailto:kelven.y...@citrix.com]
> Sent: Saturday, June 30, 2012 3:31 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate
>
>
>
> > -Original Message-
> > From: David Nalley [mailto:d
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Friday, June 29, 2012 10:37 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Hibernate
>
> On Fri, Jun 29, 2012 at 12:13 PM, Rajesh Battala
> wrote:
> >
> >
>
On Fri, Jun 29, 2012 at 12:13 PM, Rajesh Battala
wrote:
>
>
>> -Original Message-
>> From: David Nalley [mailto:da...@gnsa.us]
>> Sent: Friday, June 29, 2012 8:40 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: Hibernate
>>
>>
orate more details about the problem you were facing and why MangoDB can
solve it nicely?
Kelven
> -Original Message-
> From: Frank Zhang [mailto:frank.zh...@citrix.com]
> Sent: Thursday, June 28, 2012 6:37 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hiber
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Friday, June 29, 2012 8:40 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Hibernate
>
> On Fri, Jun 29, 2012 at 9:27 AM, Rajesh Battala
> wrote:
> >
> > Shall I pr
On Fri, Jun 29, 2012 at 9:27 AM, Rajesh Battala
wrote:
>
> Shall I proceed to replace Hibernate Framework with Spring JDBC.
>
This is not a design decision to take lightly, or rush - as we've
talked about replacing the custom ORM that CloudStack uses as well -
we'd want to make a decision on some
>
>
> Shall I proceed to replace Hibernate Framework with Spring JDBC.
>
We should rethink anything that requires raw SQL. Even object queries would be
better. At least eclipse has a way to tell you that the query and the actual
object have diverged.
--Alex
2 3:24 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate
>
> Rajesh, can you provide some rationale for this choice versus other options.
>
> -kevin
>
> > -Original Message-
> > From: Rajesh Battala [mailto:rajesh.batt...@citrix.com]
>
e don't mind it,
> > > the attach operation is quite annoying. JPA/Hibernate has a method
> > > "detach" entity, but they don't have the opposite method to 'attach'
> > > an entity. Simply google "jpa attach", there are tons of que
k to persistence. The usual
> > way is to call merge(), but it has the side effect that if you change
> > the entity accidentally, your change would be written to database, this is
> the source of mysterious bug.
> >
> >In CloudStack, you can use id(the primary
, though it's not as intuitive
> as directly wiring whole relational object in code, it does its job well in
> practice.
>
> > -Original Message-
> > From: David Avenante [mailto:d.avena...@gmail.com]
> > Sent: Thursday, June 28, 2012 4:24 PM
> > To: c
#x27;s not as intuitive as directly
wiring whole relational object in code, it does its job well in practice.
> -Original Message-
> From: David Avenante [mailto:d.avena...@gmail.com]
> Sent: Thursday, June 28, 2012 4:24 PM
> To: cloudstack-dev@incubator.apache.org
> Subject
ne 27, 2012 10:44 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: Hibernate
> >
> > Hi,
> >
> > I had started working on this issue. As Hibernate is LGPL we cannot use
> this in
> > our Apache repo.
> > I had discussed with Chiradeep an
Kelven Yang [mailto:kelven.y...@citrix.com]
> Sent: Thursday, June 28, 2012 4:00 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate
>
> A couple of points,
>
> 1. Spring is under Apache license
> 2. Spring provides pretty good JDBC wrapper like SimpleJdb
gt; Subject: RE: Hibernate
>
> Rajesh, can you provide some rationale for this choice versus other
> options.
>
> -kevin
>
> > -Original Message-
> > From: Rajesh Battala [mailto:rajesh.batt...@citrix.com]
> > Sent: Wednesday, June 27, 2012 10:44 PM
> >
Rajesh, can you provide some rationale for this choice versus other options.
-kevin
> -Original Message-
> From: Rajesh Battala [mailto:rajesh.batt...@citrix.com]
> Sent: Wednesday, June 27, 2012 10:44 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate
w about the work you were doing or planning, which is
> problematic in its own right.
>
>
> --David
>
>
>
> >> -Original Message-
> >> From: Rajesh Battala [mailto:rajesh.batt...@citrix.com]
> >> Sent: Wednesday, June 27, 2012 10:44 PM
> >&
ailto:rajesh.batt...@citrix.com]
>> Sent: Wednesday, June 27, 2012 10:44 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: RE: Hibernate
>>
>> Hi,
>>
>> I had started working on this issue. As Hibernate is LGPL we cannot use this
>> in
&
10:18 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate
>
> Sorry please ignore my former mail
>
> > > Am looking at replace Hibernate with Spring Framework
> > > simpleJDBCTemplate.
> Does this mean ripping out Hibernate? Then we don
ORM to raw
JDBC.
> -Original Message-
> From: Frank Zhang [mailto:frank.zh...@citrix.com]
> Sent: Thursday, June 28, 2012 10:11 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate
>
> Spring is able to downgrade dependency of hibernate from compile t
is distributed with
popular Linux distribution, otherwise Spring won't help.
> -Original Message-
> From: Rajesh Battala [mailto:rajesh.batt...@citrix.com]
> Sent: Wednesday, June 27, 2012 10:44 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Hibernate
>
>
e.org
> Subject: Re: Hibernate
>
> The ORM in the AWS module is 90% used by S3.
> The dependency is mostly abstracted by a DAO layer; there is another
> dependency on transactions. I believe Rajesh B is already working on this
> aspect and there is a bug open on it.
>
> --
The ORM in the AWS module is 90% used by S3.
The dependency is mostly abstracted by a DAO layer; there is another
dependency on transactions. I believe Rajesh B is already working on this
aspect and there is a bug open on it.
--
Chiradeep
On Jun 27, 2012, at 21:52, "David Nalley" wrote:
>
On Jun 28, 2012, at 12:45 AM, Sheng Liang 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
>> optional non-default part of the build.
> 3. Declare that hibernate is a system requireme
> 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
> optional non-default part of the build.
3. Declare that hibernate is a system requirement for CloudStack
I prefer option #1. It is the cleanest. I
43 matches
Mail list logo
