/jira/browse/OPENJPA-246
Project: OpenJPA
Issue Type: Improvement
Components: docs
Reporter: Pinaki Poddar
In OpenJPA, there is significant interplay between enhancement, detachment and
merge operations to support a wide variety of use cases.
Given that
[
https://issues.apache.org/jira/browse/OPENJPA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500235
]
Pinaki Poddar commented on OPENJPA-245:
---
An entity instance x which has been created by new() operator and
ersion or
detachment) only when the entity class was annotated with
@DetachedState(enabled=false)
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Aleksandar Likic [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 30, 2007 8:21 AM
To: open-jpa-dev@incubator.apache.org
Su
new
instance rather than a detached instance.
However, others may suggest ways to do what your use case requires.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Aleksandar Likic [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 2:08 PM
To: open-jpa-dev@incubator.apa
[
https://issues.apache.org/jira/browse/OPENJPA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499951
]
Pinaki Poddar commented on OPENJPA-245:
---
>From openjpa documentation (ref: 1.2. Attach Behavior)
&quo
[
https://issues.apache.org/jira/browse/OPENJPA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-245:
--
Attachment: TestMerge.zip
Attached a test case that demonstates merge() behaviour of entities
[
https://issues.apache.org/jira/browse/OPENJPA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499851
]
Pinaki Poddar commented on OPENJPA-245:
---
merge() to identify that the the merged entity instance is not
assigning an
"already existing" key is not recommneded.
If the entity is not using auto-generated, then assigning an existing
key *should* fail at commit with duplicate key exception.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Aleksandar Likic (JIRA) [mailto:[
Yes, 'svn clean' was missing.
$ svn switch /path/to/new/location
$ mvn clean package
runs successfully
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Patrick Linskey [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 24, 2007 5:48 PM
To: op
> Is it just me, or is integration-test broken?
Observed the same since did a 'svn switch'
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 24, 2007 4:07 PM
To: open-jpa-dev@incubator.apach
+1 to make the current release 1.0.0-SNAPSHOT
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On Behalf Of
Marc Prud'hommeaux
Sent: Wednesday, May 23, 2007 2:41 PM
To: open-jpa-dev@incubator.apache.org
Subject: [
This semantics of implied deletion of elements from the database as they
are removed from their collection in Java memory is supported by
@ElementDependent annotation (not pure JPA but OpenJPA)
http://incubator.apache.org/openjpa/docs/latest/manual/manual.html#depen
dent
Pinaki Poddar
BEA
> @DiscriminatorColumn(discriminatorType=DiscriminatorType.CHAR)
> @DiscriminatorValue(value="S")
The discriminator type is CHAR but the value is a String. How about
declaring the type as STRING of length 1?
@DiscriminatorColumn(discriminatorType=DiscriminatorType.STRING,
len
explictly
5. please post to open-jpa mailing list directly and *not* directly to
my mail address.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Praveen G [mailto:[EMAIL PROTECTED]
Sent: Friday, May 18, 2007 10:27 AM
To: Pinaki Poddar; open-jpa-dev@incubator.apache.org
1.5 or later.
Also recommended that you enumerate all the persistent Java classes
in in persistence.xml e.g.
com.acme.MyPOJO1
com.acme.MyPOJO2
......
Pinaki Poddar
___
Notice: This
with a simple example that
a) defines a class dynamically
b) enhances
c) defines database mapping for it
d) pouplates instance of the defined class
and finally persists it.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: James Hang [mailto:[EMAIL PROTECTED]
Sent
+1
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Craig L Russell [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 03, 2007 9:22 AM
To: open-jpa-dev@incubator.apache.org
Subject: [VOTE] Graduate from Incubation
This vote is to send the attached draft board resolution
ode.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Patrick Linskey
Sent: Wednesday, April 11, 2007 6:05 PM
To: open-jpa-dev@incubator.apache.org
Cc: cmp-dev
Subject: RE: Testing an OpenJPA module
Hi,
Pinaki's change is a big improvement. I think that we can even
Hello Craig,
Done.
Thanks for your advice.
Please review:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=2814
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 11, 2007 5:11 PM
To: open
declare all the persistent classes, the runtime is not yet
aware of/registered the aliases. Hence the error.
possible resolution:
a) declare the persistent classes in tag of persistence.xml
b) load the class before using it -- e.g. call
Class.forName("a.b.c.MyClass")
Pinaki Poddar
B
eed on contributing a patch.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 10, 2007 4:14 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Testing an OpenJPA module
FYI, Persistence is an o
> such an exhaustive list of possible problems one might run into.
Murphy's law: 'If something can go wrong, it will".
Extension to Murphy's law: "Murphy was an optimist".
:)
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: [EMAIL PR
be
loaded/invoked
When I first encountered this error, my interpreation was (b) from the
way the message was worded.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacek
Laskowski
Sent: Tuesday, April 10, 20
Hi Jeff,
I could reproduce the error on your test case. So please file a JIRA
issue.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: jeff [mailto:[EMAIL PROTECTED]
Sent: Friday, April 06, 2007 12:57 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: composite
> i can also pass along a maven2 project
Can you post the Java source of the test case and domain classes for us
to reproduce the error?
afaik, Application identity classes like PageId are not enhanced in
current versions, they used to be.
Pinaki Poddar
BEA Systems
415.402.7
you have been using.
Also can you post AbstractTransactionalCommonSpringBase.xml?
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: yangdq [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 03, 2007 2:31 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: Errors with 0.
Spring 2.0.3 can load openjpa provider runtime via
org.springframework.orm.jpa.LocalEntityManagerFactoryBean with latest
openjpa-0.9.7.
Please post stack trace and spring/jpa configuration for further
investigation.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From
persists, report with trace-level logging
(property name="openjpa.Log" value="DefaultLevel=TRACE"/>
and complete stack trace.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: jeff [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 20
t
org.apache.openjpa.jdbc.meta.FieldMapping.resolveMapping(FieldMapping.ja
va:435)
at
org.apache.openjpa.jdbc.meta.FieldMapping.resolve(FieldMapping.java:400)
at
org.apache.openjpa.jdbc.meta.ClassMapping.resolveMapping(ClassMapping.ja
va:781)
at
org.apache.openjpa.met
of primary key
used in Book.java
// the name of the variable "book" must match
the name of the variable in Page class.
}
public class Book {
@Id
String title;
}
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: jeff [
After the third execution of "mvn package -Dtest=false"
the target succeeded in creating the openjpa jars and zips.
The attendee mentioned that he had run "svn update" before building.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Patrick Li
Some of the attendees in a traininng course also experienced the same
error involving SurefireBooter.
The solution was to run "mvn package -Dtest=false" target few (3, in
this case) times.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Marc Prud'h
otated classes in the deployed unit
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On Behalf Of
Marc Prud'hommeaux
Sent: Tuesday, March 20, 2007 6:22 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Using DDL
ROM ODE_PROCESS t0 WHERE (t0.PROCESS_ID
= ?) [params=(String) { http://ode/bpel/unit-test}HelloWorld2-1]
Can you share ProcessDAOImpl and BPELDAOConnectionImpl source + your
persistence.xml?
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Matthieu Riou [mailto:[EMAI
instead of _em.persist(ret);
try
_em.merge(ret);
as ret is detached instance rather than new.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Matthieu Riou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 28, 2007 6:29 PM
To: open-jpa-dev
[
https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476790
]
Pinaki Poddar commented on OPENJPA-35:
--
Right -- a newly looked up copy (the copy comes out of L2 cache and not
Patrick,
I added the trace output of the test for "delete via query does not
remove the copy from the L2 cache".
The deleted instance was locked/modified after the transaction that
deleted it was committed.
Does that signal the L2 cache to heal itself?
Pinaki Poddar
B
[
https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-35:
-
Attachment: openjpa-35.trace.txt
Added a trace output of the test case that is failing.
shows
do you mean to lock or modify the object *after* delete?
something like:
em.begin();
em.remove(pc);
em.commit();
pc.setSomething();
em.lock(pc, READ);
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Patrick Linskey
Sent: Wednesday, February 28, 2007 2:47 PM
given test.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Patrick Linskey (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 28, 2007 2:00 PM
To: open-jpa-dev@incubator.apache.org
Subject: [jira] Commented: (OPENJPA-35) In-memory Delete operation fails
w
two consecutive
invocation are emf1,bf1 and emf2, bf2 then which of the following are
true?
a) emf1 == emf2 and bf1 == bf2
b). emf1 != emf2 but bf1 == bf2
c). emf1!=emf2 and bf1!=bf2
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Hans J. Prueller [mai
[
https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-35:
-
Attachment: openjpa-35.test.zip
Attached test case shows that after deleting via query, L2 cache
[
https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476719
]
Pinaki Poddar commented on OPENJPA-35:
--
I am not seeing this particular error anymore -- but I am seeing
ceable interface
Did the JDO solution defined its own javax.naming.spi.ObjectFactory to take
control of how JNDI-bound instances are created on lookup?
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, Februa
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar resolved OPENJPA-151.
---
Resolution: Fixed
Fixed with SVN revision 511998: http://svn.apache.org/viewvc?view=rev&
nstance of the requested object must be returned on each
lookup.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Patrick Linskey [mailto:[EMAIL PROTECTED]
Sent: Monday, February 26, 2007 11:11 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: EMF JNDI lookup is st
arsOfService>10
dept.getEmployees();
// now the dept will load a collection of all Employees
Of course, the suggested alternative approach where the application
explictly constructs this partial/filtered multi-cardinality relatinship
by choosing the elements via query is feasible and avai
the root object and fetch plan decides which subset of the
closure of this root object is realized in memory. It will surely be a
useful feature to consider expanding fetch plan with filtering criteria.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Patrick Linskey
> I should have the same code as you. Did you try changing the log
level?
Yes I too am at
$svnversion -c
406193:511043
Changing log level to error in openjpa-persistence-jdbc/pom.xml did not
impact the test failure.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
F
rby Embedded JDBC
> Driver 10.2.2.0 - (485682)).
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Michael Dick [mailto:[EMAIL PROTECTED]
Sent: Friday, February 23, 2007 11:44 AM
To: open-jpa-dev@incubator.apache.org
Subject: Re: Test failure @ svn revision 51104
)).
Will someone please verify that the tests are passing in their
environment?
Pinaki Poddar
BEA Systems
415.402.7317
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-151:
--
Attachment: PCEnhancer.AddVersion.Diff.txt
Added a public int getEnhancementContractVersion
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475144
]
Pinaki Poddar commented on OPENJPA-151:
---
One way is to add some extra checks on isPersistenceCapable() for
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475099
]
Pinaki Poddar commented on OPENJPA-151:
---
> Why will this require re-enhancem
[
https://issues.apache.org/jira/browse/OPENJPA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-151:
--
Attachment: diff.txt
Prposed changes to remove pcFlags from enhanced classes
i. remove
d *not* the original jar
3. Jar the "temp" directory
4. Overwrite the original jar, optinally
This way, if the original content contained other files (meta-inf etc.)
will be packaged exactly in the final jar.
Enhancer will not require to handle rewriting of a Jar file's conten
n the same transaction.
c) this will provide a layer of isolation to the SLSBs from the actual
implementaion of a persistence service.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Hans Prueller [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 21, 2007 1:02 AM
To: op
a jar and referred in persistence.xml in
tag. The classes will get enhanced as they are loaded in JVM
but original jar will remain unaltered.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Dain Sundstrom [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 20, 2007 10
[
https://issues.apache.org/jira/browse/OPENJPA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-147:
--
Attachment: IPerson.java
The Java interface definition is attached. I did not use an orm.xml
.
-
Key: OPENJPA-151
URL: https://issues.apache.org/jira/browse/OPENJPA-151
Project: OpenJPA
Issue Type: Improvement
Components: kernel
Reporter: Pinaki Poddar
Assigned To: Pinaki Poddar
[
https://issues.apache.org/jira/browse/OPENJPA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473293
]
Pinaki Poddar commented on OPENJPA-147:
---
I have attached four trial-and-error scenarios
Condition (a) is
[
https://issues.apache.org/jira/browse/OPENJPA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-147:
--
Attachment: TestInterface.java
> T OpenJPAEntityManager.createInstance(Class cls) fails w
[
https://issues.apache.org/jira/browse/OPENJPA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-147:
--
Attachment: iface.trace.2.txt
> T OpenJPAEntityManager.createInstance(Class cls) fails w
[
https://issues.apache.org/jira/browse/OPENJPA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-147:
--
Attachment: iface.trace.4.txt
> T OpenJPAEntityManager.createInstance(Class cls) fails w
[
https://issues.apache.org/jira/browse/OPENJPA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-147:
--
Attachment: iface.trace.1.txt
> T OpenJPAEntityManager.createInstance(Class cls) fails w
[
https://issues.apache.org/jira/browse/OPENJPA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar updated OPENJPA-147:
--
Attachment: iface.trace.3.txt
> T OpenJPAEntityManager.createInstance(Class cls) fails w
Issue Type: Bug
Components: jpa
Reporter: Pinaki Poddar
According to JavaDoc, OpenJPAEntityManager.createInstance() method
public T createInstance(Class cls);
behaves as follows:
"Create a new instance of type cls. If cls is
an interface
[
https://issues.apache.org/jira/browse/OPENJPA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469093
]
Pinaki Poddar commented on OPENJPA-117:
---
> Adding listeners should generally either be done as
[
https://issues.apache.org/jira/browse/OPENJPA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468719
]
Pinaki Poddar commented on OPENJPA-117:
---
The use case is the code that intends to register a listener but
/browse/OPENJPA-117
Project: OpenJPA
Issue Type: Improvement
Components: kernel
Reporter: Pinaki Poddar
Assigned To: Pinaki Poddar
Priority: Minor
Currently TransactionListeners can be added/removed to a broker but the list of
[
https://issues.apache.org/jira/browse/OPENJPA-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467492
]
Pinaki Poddar commented on OPENJPA-109:
---
Will you please attach a test case + annotated domain classes or
al.getFirst(), result.getFirst());
}
where in Person.java
@SqlResultSetMapping(name="SQLMapping",
[EMAIL PROTECTED](entityClass=Person.class))
Your test surely is more complex than the above. Can you send us an
isolated example test, persistence.xml and failure stack trace?
> Query updateDeptName = _em.createNativeQuery(sql,"DeptBeanMapping");
If any persistence operation using DeptBean.class preceeds this call
(e.g. _em.persist(new DeptBean())), then is there any change in
behavior?
Pinaki Poddar
BEA Systems
415.402.7317
-Original Mess
Hello Michael,
> is there any reason why we can't move the code into a more common
location?
None. I will move it to SchemaGenerator.
Thanks --
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Michael Dick [mailto:[EMAIL PROTECTED]
Sent: Thursday, Ja
st f2;
public A() {
f2 = new LinkedList();
}
}
OpenJPA will use ProxyHashSet for f1 and ProxyLinkedList for f2.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Dain Sundstrom [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 13, 2006 7:24 PM
To: ope
Issue Type: Improvement
Components: datacache
Reporter: Pinaki Poddar
Assigned To: Pinaki Poddar
OpenJPA provides pluggable mechanism to synchronize L2 caches of remote OpenJPA
runtime. The commit events from one OpenJPA runtime can propagate to other
remote OpenJPA
> This is a major hole in the JPA spec if you ask me.
Once upon a time, there was a spec called JDO. It had a API
javax.jdo.JDOHelper.getObjectId(Object pc);
I think it got left out while copying ;)
Pinaki Poddar
BEA Systems
415.402.7
incompatiable types be added, use
openjpa.ProxyManager=default(AssertAllowedType=true)
By default, the flag is false.
Pinaki Poddar
BEA Systems
415.402.7317
___
Notice: This email message, together with any attachments,
> Is there a way to extract the primary key from a persistent bean using
a spec JPA API or an API specific to OpenJPA?
OpenJPAEntityManager.getObjectId(Object pc);
This is *not* available in javax.persistence.EntityManager
Pinaki Poddar
BEA Systems
415.402.7
anism for weblogic.
Pinaki Poddar
BEA Systems
415.402.7317
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, th
I had mistakenly broadcast an unrelated mail in this forum few minutes
ago.
Sorry
Pinaki Poddar
BEA Systems
415.402.7317
___
Notice: This email message, together with any attachments, may contain
information of BEA
tion.getId().
Pinaki Poddar
BEA Systems
415.402.7317
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be co
not parsed
(or at least its first word is not analyzed) to determine whether it is
a SELECT/UPDATE/DELETE operation.
So effectively it is a bug.
I am wondering, however, whether ability to execute non-SELECT SQL query
in the same transaction will cause deeper inconsitencies.
Pinaki Poddar
B
+1
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Marc Prud'hommeaux [mailto:[EMAIL PROTECTED] On Behalf Of
Marc Prud'hommeaux
Sent: Wednesday, November 08, 2006 6:29 PM
To: open-jpa-dev@incubator.apache.org
Subject: [VOTE] publish openjpa 0.9.5-incubati
> Statement: OpenJPA should support JDK 1.4 and beyond. There is no
requirement to support the older JDK 1.3 environment.
+1
Pinaki Poddar
BEA Systems
415.402.7317
___
Notice: This email message, together with
sses before they are loaded in JVM.
c) Kodo will attempt to enhance (if -javagaent is specified) when it sees a
class (unspecified in persistence.xml) entering managed regime such as
em.persist(obj) would trigger Kodo to see if obj.class is enhanced and if not
then will try to enhance it.
P
[
http://issues.apache.org/jira/browse/OPENJPA-60?page=comments#action_12438249 ]
Pinaki Poddar commented on OPENJPA-60:
--
Fix available on revision #450632.
> Specifying the wrong persistence implementation in persistence.xml leads
[
http://issues.apache.org/jira/browse/OPENJPA-24?page=comments#action_12435915 ]
Pinaki Poddar commented on OPENJPA-24:
--
I had made certain changes for extending OpenJPA with alternative
implementaions via ProductDerivations mechanics
relation field
"father" to another Male. If recusrion-depth is set to 3 for "father" --
a Male instance will also fetch his father, grandfather and
great-grandfather.
A single depth being fetched irrespective of recursionDepth setting is
perhaps because maxFetchDepth is set
[
http://issues.apache.org/jira/browse/OPENJPA-24?page=comments#action_12432705 ]
Pinaki Poddar commented on OPENJPA-24:
--
One use case for extension of OpenJPA implementations is backward compatibility
of Kodo 4.1 with Kodo 4.0. In Kodo
Neat idea.
+1.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Patrick Linskey
Sent: Tuesday, August 29, 2006 6:01 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE: version numbers
Does anyone have any thoughts about the questions posed below? In
particular, I
: datacache, query
Environment: Only happens when DataCache is active
Reporter: Pinaki Poddar
Delete through query such as
Query query = em.createQuery("DELETE FROM Node n");
query.exe
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 h
ile object
managment being
independent of specific storage technology (a JDO legacy:).
6% code is JPA implementation following a facade pattern (available in
openjpa-persistence package) built on top of this kernel.
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message-
From: Patrick L
vaEE portal may then report how
"default behaviour of OpenJPA is not spec-compliant" :(
On performance front, initial results indicate that OpenJPA is
significantly better than other alternatives against industry standard
benchmarks -- so even leaving DataCache off would not give a reason to
95 matches
Mail list logo
