What is the error that you are seeing?
On Mon, Aug 1, 2011 at 8:03 PM, RICHARD LUONG rlu...@gmail.com wrote:
Hi,
Does Slice support using a connection pool? I was able to get the
connection pool working when not using Slice with the following
persistence-unit:
persistence-unit
I have a OneToMany relationship defined like this:
@Entity
Parent {
@OneToMany(mappedBy = parent, fetch = FetchType.LAZY, cascade = {
CascadeType.PERSIST, CascadeType.REFRESH, CascadeType.MERGE})
private ListChild childList;
// ...
@Version
private int version;
}
@Entity
I'm getting the following error:
Caused by: openjpa-2.1.0-r422266:1071316 nonfatal user error
org.apache.openjpa.persistence.ArgumentException: No slices are configured
or available
at
Any updates? Has this been tested yet?
On 06/14/2011 02:37 PM, Pinaki Poddar [via OpenJPA] wrote:
If possible, try revision 1135806 from trunk.
I have committed a draft version that would execute SQL in Slice. I
have not tested it and I have concerns about sorting etc.
If possible, let me
Any updates? Has this been tested yet?
As a brave user of Open Source software, you will be testing it, I hoped :)
Of course, It is checked-in with some degree of testing.
-
Pinaki Poddar
Chair, Apache OpenJPA Project
--
View this message in context:
Hi Bengt,
It is possible (with some effort :) to offer a different POJO y that holds
the original state of a managed POJO x *when* x entered a persistence
context. But y can not be managed by the same context, because x is already
present in that context. So y will be essentially an unmanaged
I just checked out, built and ran the code against revision 1135806.
Error is the same. Attached:
Caused by: java.lang.NullPointerException
at
org.apache.openjpa.kernel.ExpressionStoreQuery.newCompilation(ExpressionStoreQuery.java:154)
at
Hi,
I just cross checked with a native SQL query on Slice. It does run.
Though the new addition lacked thorough testing, I would not expect the
error you have reported provided the new changes are applied in your
environment.
To ensure that the change is available in your environment, please
Ok, I've found a workaround. The code seems to be failing because it cannot
determine the DBDictionary to use. It uses the ConnectionURL (null) and the
ConnectionDriverName (which points to the pool) to determine the
DBDictionary. Once that fails, it attempts to connect to the database to
try
