Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of ppoddar@bea.com designates
 66.248.192.39 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: RE: Extension to OpenJPA for distributed databases
Date: Wed, 6 Feb 2008 14:00:00 -0800
Message-ID: <3992B07C0590B548BB294D31768A1DA2D88AC5@repbex01.amer.bea.com>
In-Reply-To: <7262f25e0802061344o19408cf4te4cd6ee7cdb17484@mail.gmail.com>
Thread-Topic: Extension to OpenJPA for distributed databases
Thread-Index: AchpCYD7QTi0eP1ZTkqNly5SMa9DBQAAfnSQ
References: <3992B07C0590B548BB294D31768A1DA2D88917@repbex01.amer.bea.com>
 <7262f25e0802061232oa118114w709b416f0390b589@mail.gmail.com>
 <3992B07C0590B548BB294D31768A1DA2D88A6B@repbex01.amer.bea.com>
 <7262f25e0802061344o19408cf4te4cd6ee7cdb17484@mail.gmail.com>
From: "Pinaki Poddar" <ppoddar@bea.com>
To: <dev@openjpa.apache.org>

I will move that native XA Tx Manager to test package.
> Do the current OpenJPA 1.1.0 snapshot builds include the Slice code?
as of revision 619145, yes.

-----Original Message-----
From: Patrick Linskey [mailto:plinskey@gmail.com] 
Sent: Wednesday, February 06, 2008 3:44 PM
To: dev@openjpa.apache.org
Subject: Re: Extension to OpenJPA for distributed databases

> 1. The XA transaction manager is pluggable and not active by default.

I think that we should remove it -- I do not believe that we should have
an XA transaction manager in OpenJPA. That's not what OpenJPA does, and
there are plenty of good products out there that solve that need
already.

> > I see that you changed some stuff outside of the new openjpa-slice
> module.
> Yes. modified root pom.xml to add openjpa-slice as a module.
> I have added one chapter in the doc (ref_guide_slice.xml).

Do the current OpenJPA 1.1.0 snapshot builds include the Slice code?

-Patrick

On Feb 6, 2008 1:03 PM, Pinaki Poddar <ppoddar@bea.com> wrote:
> 1. The XA transaction manager is pluggable and not active by default.
> 2. The DistributedStoreManager in RESOURCE_LOCAL txn serailly commits 
> across all slices. This is the default behavior (same as Hibernate 
> Shards).
>
> > I see that you changed some stuff outside of the new openjpa-slice
> module.
> Yes. modified root pom.xml to add openjpa-slice as a module.
> I have added one chapter in the doc (ref_guide_slice.xml).
>
> In codebase, one and only critical change was made six weeks ago to 
> allow JDBCStoreManger to use a configuration separate from that of its

> context.
>
>
>
>
>
>
> -----Original Message-----
> From: Patrick Linskey [mailto:plinskey@gmail.com]
> Sent: Wednesday, February 06, 2008 2:33 PM
> To: dev@openjpa.apache.org
>
> Subject: Re: Extension to OpenJPA for distributed databases
>
> Hi,
>
> I see that you've gone a head and done the commit for this. Some
> questions:
>
> 1. At one point, Slice had a mock XA transaction manager in it. Has 
> this been removed? I strongly feel that OpenJPA should not be in the 
> business of XA transaction management.
>
> 2. I see that you changed some stuff outside of the new openjpa-slice 
> module. Do these changes mean that slice is now part of 1.1.0? I think

> that we might want to spend more time reviewing and discussing before 
> including this in a shipping product. One way to address this could be

> by creating a branch; another could be by leaving it in trunk but not 
> changing the build.
>
> -Patrick
>
> On Feb 6, 2008 9:10 AM, Pinaki Poddar <ppoddar@bea.com> wrote:
> > Hi,
> >   Some of you have reviewed this extension. Based on your responses,

> > I
>
> > have integrated openjpa-slice module with OpenJPA in my local 
> > environment.
> > I am planning to commit the same to the repository by end of today.
> >
> >   Regards --
> >
> >
> > -----Original Message-----
> > From: Pinaki Poddar
> > Sent: Wednesday, January 30, 2008 5:45 PM
> > To: 'dev@openjpa.apache.org'
> > Subject: Extension to OpenJPA for distributed databases
> >
> > Hi,
> >   I would like to add an extension of OpenJPA that allows an 
> > application to transact against a set of distributed, possibly 
> > hetereogenous, horizontally-partitioned databases [2]. The project 
> > is named as Slice and is similar in scope to Hibernate Shards.
> >   The development codebase so far been maintained in Apache Lab 
> > repository and given its current state I propose to add the codebase

> > to a new openajpa-slice module.
> >
> >   I request you to review current state of its implementaion [1] and

> > express your opinion/views on feasibility of my proposal.
> >
> >   Regards --
> >
> > Pinaki
> >
> > [1] Slice website:
> > http://people.apache.org/~ppoddar/slice/site/index.html
> >
> > [2] dev2dev blog:
> > http://dev2dev.bea.com/blog/pinaki.poddar/archive/2008/01/slice_open
> > jp
> > a_
> > f_1.html
> >
> > Notice:  This email message, together with any attachments, may
> contain information  of  BEA Systems,  Inc.,  its subsidiaries  and 
> affiliated entities,  that may be confidential,  proprietary, 
> copyrighted  and/or legally privileged, and is intended solely for the

> use of the individual or entity named in this message. If you are not 
> the intended recipient, and have received this message in error, 
> please immediately return this by email and then delete it.
> >
>
>
>
> --
> Patrick Linskey
> 202 669 5907
>
> Notice:  This email message, together with any attachments, may
contain information  of  BEA Systems,  Inc.,  its subsidiaries  and
affiliated entities,  that may be confidential,  proprietary,
copyrighted  and/or legally privileged, and is intended solely for the
use of the individual or entity named in this message. If you are not
the intended recipient, and have received this message in error, please
immediately return this by email and then delete it.
>


--
Patrick Linskey
202 669 5907

Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.