) 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
Subject: RE: [jira
[
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
/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
[
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
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:[EMAIL PROTECTED]
Sent
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.apache.org
Subject
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: open-jpa-dev
+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: [VOTE] move
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,
length=1)
Pinaki Poddar
it 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
or later.
Also recommended that you enumerate all the persistent Java classes
in class in persistence.xml e.g.
persisetnce-unit name=...
classcom.acme.MyPOJO1/class
classcom.acme.MyPOJO2/class
..
/persietnec-unit
Pinaki Poddar
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
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 class tag of persistence.xml
b) load the class before using it -- e.g. call
Class.forName(a.b.c.MyClass)
Pinaki Poddar
BEA Systems
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
/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, 2007 2:52 PM
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 open
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.9.7
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.7317
)
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.meta.ClassMetaData.resolve(ClassMetaData.java:1570)
...
Pinaki Poddar
BEA Systems
415.402.7317
-Original Message
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, 2007 4:12 PM
To: open-jpa-dev
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'hommeaux [mailto:[EMAIL
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 Linskey [mailto:[EMAIL
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 [mailto:[EMAIL PROTECTED]
Sent: Wednesday
for @Entity
annotated 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
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 [mailto
.
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
with active
[
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
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
BEA Systems
[
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
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
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 starting openJPA every
[
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=revrev
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, February 27, 2007 3:32 PM
To: open-jpa
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 available right now
with current features.
Pinaki Poddar
BEA Systems
415.402.7317
)).
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: diff.txt
Prposed changes to remove pcFlags from enhanced classes
i. remove
[
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-enhancement
[
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
[
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
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: open-jpa-dev
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 content.
Pinaki Poddar
BEA Systems
415.402.7317
[
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
[
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 T OpenJPAEntityManager.createInstance(ClassT cls) fails when
[
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 T OpenJPAEntityManager.createInstance(ClassT cls) fails when
[
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 T OpenJPAEntityManager.createInstance(ClassT cls) fails
/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
[
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
[
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
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 Message-
From: George
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, January 04
;
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: open-jpa
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.7317
().
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 confidential
[
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
a 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 to 1.
Pinaki
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
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
report otherwise.
Pinaki Poddar
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 Linskey
Sent: Friday
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
61 matches
Mail list logo
