openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Prud'hommeaux <>
Subject Re: Inconsistent lazyload between runtime / compiletime enhancement
Date Mon, 16 Jul 2007 02:11:46 GMT

To really determine if it is a difference between runtime enhancement  
vs. compiletime enhancement, you should try to run your standalone  
test case using runtime enhancment. E.g. instead of running the  
enhancer at build time, you should instead specify "-javaagent:/path/ 
to/openjpa.jar", which will cause the enhancement to happen at runtime.

If you are still seeing differences between when you run your test  
case with compiletime and runtime enhancement, then we can dig deeper  
to figure out what it going on.

On Jul 15, 2007, at 7:04 PM, mikecool wrote:

> Hi All,
> I am working on a project to migrate several applications from EJB  
> 2.1 to
> 3.0. The entire entity beans will be removed, and add new POJO
> implementation against JPA implementation which is OpenJPA 0.9.7 on  
> WebLogic Server 10.
> I found an interesting thing that is the lazyload enhancement  
> doesn't work
> within container. Since we can't compile test code after  
> enhancement, we let
> this for container.
> Meanwhile, I tried to make a similar pojo test environment with  
> same code
> base and db. It works well.
> The major differences between these two is Runtime / Compiletime
> enhancement. Does anyone find the same issue?
> *: the entities have a little complex hierarchy and embeddable  
> object as
> primary id.
> -- 
> View this message in context: 
> lazyload-between-runtime---compiletime-enhancement- 
> tf4084155.html#a11608175
> Sent from the OpenJPA Users mailing list archive at

View raw message