| Is Load Time Weaving required? [message #11984] |
Mon, 30 June 2008 17:39  |
Eclipse User |
|
|
|
Hi,
When using EclipseLink in a Spring environment is it necessary to
configure Load Time Weaving (LTW)?
Btw, excuse my ignorance, but I was unaware until I started exploring
Spring that LTW was an issue with JPA. Indeed I do not have to take
special action when I am using JPA in a J5EE app server, but that may
well be because JPA is native to the environment. What really makes
me wonder is that Googling for:
+JPA "Load Time Weaving" LTW -spring
brings back only a few hits. Is this a Spring specific issue? Yes,
yes, I know, I should be asking this on the Spring Forum :-)
Thanks,
Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Too
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
|
| Re: Is Load Time Weaving required? [message #12047 is a reply to message #12021] |
Tue, 01 July 2008 16:23  |
| Eclipse User |
|
|
|
The biggest benefit to LTW is the simplicity of development. The byte
codes compiled are the ones you package and deploy.
Static weaving introduces another development step but may be necessary if
you want the same packaged app to run in a number of environments,
including some where LTW is not an option.
Doug
|
|
|
| Re: Is Load Time Weaving required? [message #563952 is a reply to message #11984] |
Tue, 01 July 2008 04:23 |
| Eclipse User |
|
|
|
Joel,
Load-Time or Dynamic weaving is not strictly required but generally
recommended. Using EclipseLink JPA's weaving support enables several
useful features:
- 1:1 and M:1 lazy loading
- Transparent Fetch Groups
- Optimized change tracking of managed entities in a transaction
When used within an EJB3 container the weaving is done automatically. If
using EclipseLink in another container then a java-agent allows dynamic
weaving to be used. Within Spring their java-agent is tied into our
weaving solution.
NOTE: We also support static weaving for containers where an agent is not
an option.
Doug
http://wiki.eclipse.org/Introduction_to_EclipseLink_Applicat ion_Development_(ELUG)#Using_Weaving
|
|
|
| Re: Is Load Time Weaving required? [message #563975 is a reply to message #12008] |
Tue, 01 July 2008 06:04 |
| Eclipse User |
|
|
|
Hi Doug,
Thanks for the reply.
After reading up on the Spring LTW yesterday I am concerned about the
deploy time implications of using dynamic weaving. My goal is that ORMF
be deployable in any compliant web container it appears that there are
configurations differences, when depending on LTW, with Spring
depending on the environment. To avoid this I think that we would be
better off using static compile time weaving. Do you concur or are
there benefits to dynamic weaving that I am overlooking?
Thanks,
Joel
|
|
|
| Re: Is Load Time Weaving required? [message #564011 is a reply to message #12021] |
Tue, 01 July 2008 16:23 |
| Eclipse User |
|
|
|
The biggest benefit to LTW is the simplicity of development. The byte
codes compiled are the ones you package and deploy.
Static weaving introduces another development step but may be necessary if
you want the same packaged app to run in a number of environments,
including some where LTW is not an option.
Doug
|
|
|
Powered by
FUDForum. Page generated in 0.05590 seconds
Home