On Feb 27, 2007, at 11:16 AM, Marc Prud'hommeaux wrote:
All-
I noticed recently that the continuum build at http://
vmbuild.apache.org/continuum is back up and running again
(hooray!). However, it is failing for OpenJPA because we have a new
sub-module, called "openjpa-examples", which I b
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-160:
Attachment: openjpa-160-clone-patch.txt
This patch will clone BrokerImpls from a template
David-
Thanks for fixing it! I'll make a JIRA entry in the future.
The "OpenJPA Distribution" module seems to hang now though. I'm
not sure how long it's supposed to take.
Weird ... it built the binary fine, but then it seemed to hang. If it
happens for the next build, I'll try to poke ar
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Wisniewski updated OPENJPA-160:
---
Attachment: profile_clonepatch.jpg
Guys... sorry to keep bearing bad news, but we seem to ju
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476626
]
Rob Wisniewski commented on OPENJPA-160:
Okay.. looks like the finalizer was the problem. I took it out an
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476627
]
Rob Wisniewski commented on OPENJPA-160:
Also, to be clear, the cloning seems to give us a little boost too
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476629
]
Patrick Linskey commented on OPENJPA-160:
-
K... IMO, we should get rid of the finalizer in the default confi
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-160:
Attachment: openjpa-160-finalization-and-cloning-patch.txt
- moved BrokerImpl.finalize() t
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476680
]
Rob Wisniewski commented on OPENJPA-160:
Patrick.. good work. The new patch performs as expected. I test
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey resolved OPENJPA-160.
-
Resolution: Fixed
Hopefully, we can put this to rest now.
> Reuse BrokerImpl objects
>
Good catch; I wrote that before the finalization changes went in.
Changing...
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of BEA Syste
+public Object newInstance(String clsName, Class type,
Configuration conf,
+boolean fatal) {
+if (BrokerImpl.class.getName().equals(clsName)) {
+// This is not synchronized. If there are concurrent
invocations
+// while _templateBroker is null, we'
> Cloneable _templateBroker = null;
> boolean _templateTried = false;
> if (broker instanceof Cloneable)
> _templateBroker = (Cloneable) broker;
Since BrokerImpl is Cloneable, and the property always returns a
BrokerImpl, I don't think that we need to check for cloneability.
-Patri
[
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 somethi
[
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
> EntityManagerFactory emf =
OpenJPAPersistence.createEntityManagerFactory(EMF_JNDI_LOCATION,
(Context) null);
1. Instead of passing null context, if the same Context instance is
passed on every invocation -- does the behaviour change?
2. If the emf and its underlying brokerfactory bf from two con
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476731
]
Craig Russell commented on OPENJPA-160:
---
>K... IMO, we should get rid of the finalizer in the default config,
[
https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476732
]
Patrick Linskey commented on OPENJPA-35:
What happens if the user modifies the object or if the user obtains
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476736
]
Patrick Linskey commented on OPENJPA-160:
-
> 1. I really think we're going just a bit too fast here. I wasn'
[
https://issues.apache.org/jira/browse/OPENJPA-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476737
]
Kevin Sutter commented on OPENJPA-149:
--
Brad,
For now, go ahead and use the workaround as documented by Patrick
The issue is now better be stated as "Delete by Query does not remove
the copy from L2 cache".
a) Tried to lock the instance, before delete causes commit to fail
with OptimisticVerification
b) Modifying the object before delete causes no change in behaviour
in the scope of the given test.
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476744
]
Kevin Sutter commented on OPENJPA-160:
--
> IIRC, we're operating in a commit-then-review mode in OpenJPA. This i
I was referring to subsequent transactions after the delete. The delete
happens in its own persistence context, meaning that anything that has
happened in the transaction to date is basically ignored.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476749
]
Patrick Linskey commented on OPENJPA-160:
-
> The extra day would have allowed Abe to get his comments recogn
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
To
I'm wondering whether or not the cache is properly healing itself, which
gives us a feel for how severe the problem is.
> em.begin();
> em.remove(pc);
> em.commit();
>
> pc.setSomething();
> em.lock(pc, READ);
I am interested in the behavior when using delete-by-query, as I'm
pretty sure that I
[
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 t
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
415.40
[
https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476773
]
Patrick Linskey commented on OPENJPA-35:
I haven't looked at your test, but I'm guessing that since it has a
[
https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476774
]
Patrick Linskey commented on OPENJPA-35:
... to finish that thought, I'd then expect that the instance would
[
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
[
https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476794
]
Patrick Linskey commented on OPENJPA-35:
Well, I think that it's worth *fixing*, and shouldn't really be all
[
https://issues.apache.org/jira/browse/OPENJPA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-125:
Affects Version/s: 1.0.0
> OpenJPA-specific metadata cannot be specified in XML descriptor
[
https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-35:
---
Fix Version/s: 0.9.7
Affects Version/s: 0.9.6
> In-memory Delete operation fails with
[
https://issues.apache.org/jira/browse/OPENJPA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-125:
Fix Version/s: 1.0.0
Affects Version/s: (was: 1.0.0)
0.9
[
https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-35:
---
Affects Version/s: 0.9.0
> In-memory Delete operation fails with active DataCache
> -
[
https://issues.apache.org/jira/browse/OPENJPA-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-89:
---
Fix Version/s: 0.9.7
> Bulk delete fails to delete owned many-to-many relationship (entry rem
[
https://issues.apache.org/jira/browse/OPENJPA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-135:
Fix Version/s: 0.9.7
> join fetch not returning duplicate references which not conforming
[
https://issues.apache.org/jira/browse/OPENJPA-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-17:
---
Fix Version/s: 0.9.7
> bad sql with missing subquery produced with query with nested subqueri
[
https://issues.apache.org/jira/browse/OPENJPA-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-148:
Fix Version/s: 0.9.7
> Parsing exception while using an "exploded" archive
> -
[
https://issues.apache.org/jira/browse/OPENJPA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-134:
Fix Version/s: 0.9.7
> Extra unneeded SQL joins for OneToMany relationship with fetch type
[
https://issues.apache.org/jira/browse/OPENJPA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-49:
---
Fix Version/s: 0.9.7
> bad sql pushdown, should use inner joins but has no joins, just uses f
[
https://issues.apache.org/jira/browse/OPENJPA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-142:
Fix Version/s: 0.9.7
> Entity name is ignored when specified in the orm.xml file
> ---
[
https://issues.apache.org/jira/browse/OPENJPA-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-26:
---
Fix Version/s: 0.9.7
> JPQL parser failed to handle unary operations in arithmetic comparison
[
https://issues.apache.org/jira/browse/OPENJPA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-152:
Fix Version/s: 0.9.7
> Warn or throw an exception when a persistence unit has multiple nam
[
https://issues.apache.org/jira/browse/OPENJPA-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-75:
---
Fix Version/s: 0.9.7
> error message for missing query id var needs improvement
> ---
[
https://issues.apache.org/jira/browse/OPENJPA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-23:
---
Fix Version/s: 0.9.7
> -418 sqlexception using DB2 and EJB QL with SQRT or MOD
>
[
https://issues.apache.org/jira/browse/OPENJPA-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-113:
Fix Version/s: 0.9.7
> when you specify columm table="empbean" in the xml file entity id
[
https://issues.apache.org/jira/browse/OPENJPA-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-18:
---
Fix Version/s: 0.9.7
> bulk update to Entity with secondary table mapping produces BAD SQL
>
[
https://issues.apache.org/jira/browse/OPENJPA-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-28:
---
Fix Version/s: 0.9.7
> groupby clause of a subquery incorrectly duplicated in the main query
[
https://issues.apache.org/jira/browse/OPENJPA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-51:
---
Fix Version/s: 0.9.7
> bad sql pushdown, sub select is missing from clause
>
[
https://issues.apache.org/jira/browse/OPENJPA-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-80:
---
Fix Version/s: 0.9.7
> Bad Escaping for LIKE in MySQL
> --
>
>
[
https://issues.apache.org/jira/browse/OPENJPA-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-78:
---
Fix Version/s: 0.9.7
> Automatic runtime enhancement only works when the class is listed in t
[
https://issues.apache.org/jira/browse/OPENJPA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-9:
--
Fix Version/s: 0.9.7
> PCEnhancer not processing multiple PU's defined within a single
> persis
[
https://issues.apache.org/jira/browse/OPENJPA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-46:
---
Fix Version/s: 0.9.7
> true, false not case insensitive, gets null pointer exception
> --
[
https://issues.apache.org/jira/browse/OPENJPA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-143:
Fix Version/s: 0.9.7
> Problems with Single Table Inheritance Strategy (and Discriminator
[
https://issues.apache.org/jira/browse/OPENJPA-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-112:
Fix Version/s: 0.9.7
> Native queries and named parameters: poor error message
> -
[
https://issues.apache.org/jira/browse/OPENJPA-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-83:
---
Fix Version/s: 0.9.7
> Bad SQL for Subselect BETWEEN
> -
>
>
[
https://issues.apache.org/jira/browse/OPENJPA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-57:
---
Fix Version/s: 0.9.7
> persistence_1_0.xsd is missing
> --
>
>
[
https://issues.apache.org/jira/browse/OPENJPA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-132:
Fix Version/s: 0.9.7
> java.lang.NoSuchMethodError for entity with ID of type java.sql.Dat
[
https://issues.apache.org/jira/browse/OPENJPA-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-22:
---
Fix Version/s: 0.9.7
> locate & substring queries fail both db2 & derby, cannot use parameter
[
https://issues.apache.org/jira/browse/OPENJPA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey resolved OPENJPA-153.
-
Resolution: Fixed
I believe that the only remaining issue here is captured in OPENJPA-14
[
https://issues.apache.org/jira/browse/OPENJPA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-147:
Fix Version/s: 1.0.0
> T OpenJPAEntityManager.createInstance(Class cls) fails when T is
[
https://issues.apache.org/jira/browse/OPENJPA-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-145:
Fix Version/s: 1.0.0
> support Java5 wildcard on OpenJPA
> ---
[
https://issues.apache.org/jira/browse/OPENJPA-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey resolved OPENJPA-93.
Resolution: Fixed
The feature works, but OPENJPA-149 currently prevents it from working in
[
https://issues.apache.org/jira/browse/OPENJPA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-84:
---
Fix Version/s: 1.0.0
> Escape sql reserved words in column names
> --
[
https://issues.apache.org/jira/browse/OPENJPA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-71:
---
Fix Version/s: 0.9.7
What happens if openjpa.DynamicDataStructs is enabled?
> Caching primit
[
https://issues.apache.org/jira/browse/OPENJPA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-123:
Component/s: build / infrastructure
> Test framework should allow tests that are expected
[
https://issues.apache.org/jira/browse/OPENJPA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476808
]
Craig Russell commented on OPENJPA-35:
--
I agree this bug is worth fixing and pending the fix, worth documenting
[
https://issues.apache.org/jira/browse/OPENJPA-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-38:
---
Fix Version/s: 1.0.0
> Force field writes on update
>
>
>
[
https://issues.apache.org/jira/browse/OPENJPA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-86:
---
Fix Version/s: 1.0.0
Affects Version/s: 0.9.6
> "uuid-hex" generator does not make af
[
https://issues.apache.org/jira/browse/OPENJPA-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-120:
Fix Version/s: 0.9.7
> For Multi Table Entity subselect with field in second table gets DB
[
https://issues.apache.org/jira/browse/OPENJPA-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-87:
---
Fix Version/s: 1.0.0
Affects Version/s: 0.9.0
0.9.6
> openjpa
[
https://issues.apache.org/jira/browse/OPENJPA-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-44:
---
Fix Version/s: 0.9.7
> metadata-complete element in orm.xml is ignored
>
[
https://issues.apache.org/jira/browse/OPENJPA-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-121:
Fix Version/s: 0.9.7
> Table name defaults to the class name instead of the entity name
>
[
https://issues.apache.org/jira/browse/OPENJPA-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-81:
---
Fix Version/s: 0.9.7
> Bad error message when trying to query a Collection relation using dot
[
https://issues.apache.org/jira/browse/OPENJPA-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-19:
---
Fix Version/s: 0.9.7
> 1.5F gets translated to BigDecimal(1.5) when used as literal in EJB QL
[
https://issues.apache.org/jira/browse/OPENJPA-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476812
]
Patrick Linskey commented on OPENJPA-20:
I think of this as a feature, not a bug. Thoughts?
> Query can retu
[
https://issues.apache.org/jira/browse/OPENJPA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-152:
Component/s: query
logging
Priority: Minor (was: Major)
> Warn or
[
https://issues.apache.org/jira/browse/OPENJPA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476813
]
Patrick Linskey commented on OPENJPA-152:
-
+1 to throwing an exception rather than logging.
> Warn or throw
[
https://issues.apache.org/jira/browse/OPENJPA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-9:
--
Priority: Minor (was: Major)
> PCEnhancer not processing multiple PU's defined within a single
[
https://issues.apache.org/jira/browse/OPENJPA-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-148:
Priority: Minor (was: Major)
> Parsing exception while using an "exploded" archive
>
[
https://issues.apache.org/jira/browse/OPENJPA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-46:
---
Priority: Minor (was: Major)
> true, false not case insensitive, gets null pointer exception
[
https://issues.apache.org/jira/browse/OPENJPA-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-78:
---
Priority: Minor (was: Major)
> Automatic runtime enhancement only works when the class is li
[
https://issues.apache.org/jira/browse/OPENJPA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-132:
Priority: Minor (was: Major)
> java.lang.NoSuchMethodError for entity with ID of type jav
[
https://issues.apache.org/jira/browse/OPENJPA-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-112:
Priority: Minor (was: Major)
> Native queries and named parameters: poor error message
>
[
https://issues.apache.org/jira/browse/OPENJPA-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-75:
---
Priority: Minor (was: Major)
> error message for missing query id var needs improvement
> --
[
https://issues.apache.org/jira/browse/OPENJPA-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-93:
---
Fix Version/s: 0.9.7
> Sequence generation in a JTA environment should not require non-JTA da
[
https://issues.apache.org/jira/browse/OPENJPA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-153:
Fix Version/s: 0.9.7
> WebSphere and non-jta-data-source and default ManagedRuntime
>
[
https://issues.apache.org/jira/browse/OPENJPA-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-113:
Priority: Minor (was: Major)
> when you specify columm table="empbean" in the xml file e
[
https://issues.apache.org/jira/browse/OPENJPA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-105:
Component/s: build / infrastructure
> Put together a test suite for Enhancer
> ---
[
https://issues.apache.org/jira/browse/OPENJPA-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-33:
---
Component/s: build / infrastructure
> Need Query Engine test bucket
> ---
[
https://issues.apache.org/jira/browse/OPENJPA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-137:
Fix Version/s: 1.0.0
> Perform parameter validation for annotated callback methods
> -
[
https://issues.apache.org/jira/browse/OPENJPA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-5:
--
Component/s: build / infrastructure
> OpenJPA doesn't compile with JDBC 4
>
[
https://issues.apache.org/jira/browse/OPENJPA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-91:
---
Fix Version/s: 0.9.7
> java.lang.VerifyError on websphere after application reload
>
[
https://issues.apache.org/jira/browse/OPENJPA-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-79:
---
Component/s: build / infrastructure
> Please add Eclipse artifacts to svn ignore
> --
Hi,
I'm going back at the OpenJPA implementation for the Apache ODE project and
am still having problems with the setup. Whan I try to persist a new object
I get an exception "Attempt to persist detached object". I guess the when I
instantiate my object OpenJPA can't locate its transactional cont
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@incubator.apache.org
Thanks! But shouldn't I worry about the fact that a brand new instance is
detached? I could be wrong but it looks like it's more a symptom of
something wrong in my configuration, no?
On 2/28/07, Pinaki Poddar <[EMAIL PROTECTED]> wrote:
instead of _em.persist(ret);
try
_em.merge(ret);
as re
Can you post the source for ProcessDAOImpl? Also, are there any other
OpenJPA properties in your configuration? Finally, I'm assuming that
you're using a somewhat-current 0.9.7-SNAPSHOT. Correct me if I'm wrong.
> But shouldn't I worry about the fact that a brand new
> instance is detached? I cou
1 - 100 of 104 matches
Mail list logo
