I am using OpenJPA 1.2.3 and am enabling the data cache. I'm setting up the
refresh so that it will clear the cache once per day using the cron-like
setting. How is OpenJPA going to do this? Is it going to create a separate
thread that will sleep and wake up, is there some code running checking
I am using OpenJPA 1.2.3 in WebSphere 7. I have an entity that I have added
an entity listener via annotation. In the entity listener class, I have
defined PostPersist, PostUpdate, and PostRemove methods.
I am using a web service. Within the web service lifecycle, there are two
different
I'm not using either a data cache or a query cache. Do you mean
IgnoreChanges? I set a value of IgnoreChanges=true, and that caused the
first call to go away. However, that doesn't work for me, since I can't
always assume my object isn't dirty - methods earlier in my transaction may
have
Not a true problem I don't think, but a curiosity.
I am using the version of JPA 1.2.3-SNAPSHOT which is included in WebSphere
7.
I have a base class that contains common fields, such as id, insert user,
insert datetime, etc, and this is annotated as @MappedSuperclass. My
entities all extend
FindBugs runs against the class files. We are running this from Jenkins, and
are using Maven to do the build. So, we've got Maven set up to do
compile-time enhancement. To check against unenhanced classes, we'd have to
do something like creating two different builds using different Maven
Oracle. Other databases might have a different type names for XML columns so
you're losing a little portability with this approach.
At any rate, I'm glad it worked for you.
-mike
On Fri, Mar 25, 2011 at 3:14 PM, kostellodon [hidden
email]/user/SendEmail.jtp?type=nodenode=6209080i=0by-user=twrote
I am working with base WebSphere 7, which includes JPA 1.2.1, and am
interacting with an Oracle 11.2 database. I have a table with an XMLType
column in it that I am trying to persist and later retrieve from. I am
doing my testing using JUnit 4, using ojdbc6.11.1.0.7.0.jar for my driver.
My
by WebSphere on a
regular basis (but you might need the latest fixpack).
Hope this helps,
-mike
On Fri, Mar 25, 2011 at 11:47 AM, kostellodon [hidden
email]/user/SendEmail.jtp?type=nodenode=6208737i=0by-user=twrote:
I am working with base WebSphere 7, which includes JPA 1.2.1, and am
interacting
I'm doing this query within a unit test, and am using runtime enhancement via
the javaagent.
I've tried this with both 1.2.2 and 2.1.0 and see the same index out of
bounds exception in both cases.
Either querying another timestamp field or removing the version annotation
from the update field
Hmm, further information comes out. It seems to work with mine when I have
the field directly in my entity. In my standard case, I have a basic entity
that my standard entities extend. I have reduced by base entity to the
following:
@MappedSuperclass
public abstract class BasicEntity {
I am using JPA 1.2.1 I have an entity with an update time field of type
Timestamp that is annotated as the version field. I am trying to create a
query to find all entities of this type that were updated before a certain
time. When getting the result list from the query, I get an exception.
11 matches
Mail list logo
