Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » Is Load Time Weaving required?
Is Load Time Weaving required? [message #376055] Mon, 30 June 2008 21:39 Go to next message
Joel Rosi-Schwartz is currently offline Joel Rosi-SchwartzFriend
Messages: 624
Registered: July 2009
Location: London. England
Senior Member
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 #376061 is a reply to message #376055] Tue, 01 July 2008 08:23 Go to previous messageGo to next message
Doug Clarke is currently offline Doug ClarkeFriend
Messages: 155
Registered: July 2009
Senior Member
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 #376063 is a reply to message #376061] Tue, 01 July 2008 10:04 Go to previous messageGo to next message
Joel Rosi-Schwartz is currently offline Joel Rosi-SchwartzFriend
Messages: 624
Registered: July 2009
Location: London. England
Senior Member
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 #376071 is a reply to message #376063] Tue, 01 July 2008 20:23 Go to previous message
Doug Clarke is currently offline Doug ClarkeFriend
Messages: 155
Registered: July 2009
Senior Member
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
Previous Topic:Why choose EclipseLink rather than vinilla JPA, e.g. TopLink, Hibernate etc.
Next Topic:Probem getting basic sample running
Goto Forum:
  


Current Time: Thu Apr 25 19:54:00 GMT 2024

Powered by FUDForum. Page generated in 0.02766 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top