Hi Ron,
The WebSphere JPA documentation relies on the Apache OpenJPA documentation
(and the JPA specification itself) for much of the documentation. We
didn't want to repeat (and maintain) all of the information that was
already available.
But, what is documented in the WebSphere InfoCenter are t
Hi Ron,
The RuntimeUnenhancedClasses "feature" was an attempt to provide JPA ORM
capabilities without using bytecode enhancement techniques. Instead,
dynamic subclasses were generated which attempted to provide the same level
of functionality. This "feature" never got the necessary attention to m
Sounds reasonable. Historically have issues been the only thing that have
prompted new snapshots of OpenJPA 2.0.x to be included in WAS7 fixpacks? If the
OpenJPA community writes a new whiz-bang feature in the 2.0.x stream could it
qualify for inclusion in a fixpack or has WAS7+OpenJPA 2.0.x ent
I've just recently started using OpenJPA and from a new user perspective I
interpreted "openjpa.RuntimeUnenhancedClasses=supported" to mean first check if
the code is running within an app server and let the app server enhance the
classes *then* fallback and actually do a runtime enhancement. It
Hi Ron,
WebSphere continues to support their JPA solutions via improvements to the
corresponding OpenJPA offerings. The OSGi/JPA 2.0 Feature Pack is based on
the OpenJPA 2.0.x service stream. WebSphere's v8 solution is based on the
OpenJPA 2.1.x service stream.
If issues are discovered in any of
I couldn't find anything on the OpenJPA or IBM WAS website(s) about how/if/when
IBM decides to package OpenJPA improvements into future feature packs. Does
anyone know if a future WAS7 feature pack will include OpenJPA 2.1.x? Along
those same lines, is WAS8's JPA implementation based on OpenJPA
Hi,
The customer has the same database, the same application (same build and stuff
like that) and same everything. This is what freaks me out ;-) Of course
something must be different...
I compared the schema several times and they are the same.
Turning on Trace is quite impossible on a product
Hi Marc,
I'm not seeing anything wrong with your object model definition. But, it
definitely looks like OpenJPA is getting confused on this join column
reference (string id) and the type of the primary key (long). Have you
been able to verify that the database schemas are consistent with the
obje
Hi,
me again. This time with something i also dont get.
OrderPosition.class
---
@XmlTransient
@ManyToOne
@JoinColumn(name = "con_ship_id", referencedColumnName = "id")
ContainerShipment containerShipment;
ContainerShipment.class
---
Hi Pinaki,
your proposal led me to the solution. The good news is: I can track the changes
by changing the code the way you proposed.
What puzzled me and made me think that this must be a bug in OpenJPA is the
fact that the field "stringAttributes" was marked as dirty but the Map from the
oldS
I apologize to everyone. I just found out that the performance problems
were caused by having set a log level to TRACE. When I changed that to
INFO, the response time for retrieving 5800 rows shrunk to less than 200 ms.
When running the query in my JUnit test I was already using a log level of
INF
Here is an update reflecting my latest findings.
It seems I only get bad performance when running inside Karaf. E g
retrieving all rows in the table (5800) takes about 130 ms when I run the
query as a JUnit test. In this case I do not use a JTA. I use the entity
manager's transaction support.
Whe
12 matches
Mail list logo
