You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@openjpa.apache.org by mikecool <ge...@hotmail.com> on 2007/07/16 04:04:37 UTC
Inconsistent lazyload between runtime / compiletime enhancement
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 BEA
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: http://www.nabble.com/Inconsistent-lazyload-between-runtime---compiletime-enhancement-tf4084155.html#a11608175
Sent from the OpenJPA Users mailing list archive at Nabble.com.
Re: Inconsistent lazyload between runtime / compiletime enhancement
Posted by mikecool <ge...@hotmail.com>.
You are quite right, I follow your instruction. By specifying "-javaangent",
I enabled runtime enhancement in POJO environment. And the result is exact
same with compiletime enhancement. Thus, it issue is not the issue of
OpenJPA. I will contact BEA, seems they will dig the issue.:)
Thanks, Mike.
Gene
Marc Prud'hommeaux wrote:
>
> Mike-
>
> 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.
>
>
>
>
>
--
View this message in context: http://www.nabble.com/Inconsistent-lazyload-between-runtime---compiletime-enhancement-tf4084155.html#a11608632
Sent from the OpenJPA Users mailing list archive at Nabble.com.
Re: Inconsistent lazyload between runtime / compiletime enhancement
Posted by Marc Prud'hommeaux <mp...@apache.org>.
Mike-
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
> BEA
> 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: http://www.nabble.com/Inconsistent-
> lazyload-between-runtime---compiletime-enhancement-
> tf4084155.html#a11608175
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>