openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey" <>
Subject RE: Data + Query cache
Date Fri, 25 Aug 2006 16:31:33 GMT
(Performance pack is Kodo parlance, and this is a Kodo-related email.)

Actually, we're getting rid of Performance Pack altogether, at long last,
and replacing with a Professional Edition. (I never much liked the
Performance Pack name, given that the other two were editions.) I don't
remember the details of what lands where, but we aren't going to be selling
things that are available in OpenJPA.

You can get a feeling for what the JDO bindings for Kodo look like by taking
a look at the openjpa-persistence and openjpa-persistence-jdbc modules in
OpenJPA -- you'll notice that the bindings largely add spec behavior to the
core kernel. So the features available in the core kernel are available to
all bindings.


Patrick Linskey
BEA Systems, Inc. 

> -----Original Message-----
> From: Marc Logemann [] 
> Sent: Friday, August 25, 2006 7:01 AM
> To:
> Subject: Re: Data + Query cache
> Hi,
> does that mean that the performance pack gets obsolete or how do you  
> want to control the cache then?
> It would be weird to sell the cache to JDO users while its free for  
> JPA users right?
> --
> regards
> Marc Logemann
> [blog]
> [busn]
> Am 24.08.2006 um 22:54 schrieb Abe White:
> > How does the list feel about turning the L2 data and query caches  
> > on by default?  Traditionally, Kodo always left them off by  
> > default, primarily because they required a "performance pack"  
> > license to run.
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.

View raw message