[ http://issues.apache.org/jira/browse/OPENJPA-14?page=all ]
Patrick Linskey closed OPENJPA-14.
--
Assignee: Patrick Linskey (was: Bryan Noll)
Use the class's classloader in environments when service lookups should be
looking in the OpenJPA
Is there a way to query OpenJPA if the result came from the cache? Or
are partial cache results possible, thus making such a isCached()
method impossible to implement.
--
regards
Marc Logemann
[blog] http://www.logemann.org
[busn] http://www.logentis.de
Am 25.08.2006 um 14:39 schrieb Kevin
Problem detecting parent's access type with runtime enhancement.
-
Key: OPENJPA-34
URL: http://issues.apache.org/jira/browse/OPENJPA-34
Project: OpenJPA
Issue Type: Bug
I've no idea about that particular message, but in my experience it
sometimes takes a few runs to get mvn to run the first time, since both the
apache and ibiblio repositories are a tad flaky.
BTW, what's the version of your mvn? (mvn -v) Mine is 2.0.4.
-Patrick
--
Patrick Linskey
BEA Systems,
(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
Hi,
of course my intention wasnt to ask about kodo, but i was confused
that a feature will be on by default that was formerly on sale.
I will look into the packages to get an idea.
The other question regarding the cache or a method like isCached()
was to solve the issue that users could
DataCache or L2 cache being a performance optimization feature not
mandated by the spec, makes it a candidate for *not* being on by
default.
a) If the user explictly turns the feature on, it makes him/her aware of
its advantages as well as behavioral difference e.g. refresh().
b) If the user
inline...
Pinaki Poddar wrote:
DataCache or L2 cache being a performance optimization feature not
mandated by the spec, makes it a candidate for *not* being on by
default.
a) If the user explictly turns the feature on, it makes him/her aware of
its advantages as well as behavioral difference
On the other hand, if the feature is on by default what would be the
likely reason to turn it off? Some JavaEE portal may then report how
default behaviour of OpenJPA is not spec-compliant :(
How is the data cache not spec-compliant?
-Patrick
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
I did not mean it is. I was just how a some JavaEE portal may spin it!
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Patrick Linskey
Sent: Friday, August 25, 2006 11:22 AM
To: open-jpa-dev@incubator.apache.org
Subject: RE: Data + Query cache
On the other hand,
Hi,
sounds like you guys did a good job in factoring out the persistence
specs / APIs from the core.
--
regards
Marc Logemann
[blog] http://www.logemann.org
[busn] http://www.logentis.de
Am 25.08.2006 um 20:25 schrieb Pinaki Poddar:
94% of codebase (in terms of filesize) are independent
I think the first time users are going to write simple
applications while
evaluating . Will caching affect these kind of applications
which have a
small amount of data to play around with?
Typically, no.
-Patrick___
Hi,
is there a need to have a 3rd party regex lib these days? I am a fan
of projects not needing too much 3rd party jars.
Also i noticed many invalid javadoc usages like @author tag in method
doc sections. IMO this is invalid and causes IDEA to turn red which
in fact is ugly because one
14 matches
Mail list logo
