Hi All,
FYI: Cay is correct. The agent is used to do weaving.
Currently we weave OneToOne and ManyToOne mappings that are set as LAZY.
Our weaving makes the following changes:
1. adds an instance variable for each LAZY OneToOne or ManyToOne that
allows us to defer the loading of that attribute until it is required
2. adds getter and setter methods for those new instance variables that
are used internally to control how the attribute is loaded
3. changes some assignments within the class to call those new methods
The system property toplink.weaving.output.path can be used to provide a
location where weaved class files will be output. (i.e.
-Dtoplink.weaving.output.path=<myPath>) Support for this feature is
still fairly rudidmentary, but eventually, this feature will be used to
allow users to pre-weave classes so they can be deployed without the
agent, but still function in a LAZY manner.
-Tom
Eduardo Pelegri-Llopart wrote:
>Yesterday TheAquarium did a quick spotlight on Cay's article on
>toplink-essentials-agent [1]... is there a good description of the
>functionality and how it is accomplished?
>
>Thanks,
> - eduard/o
>
>[1]
>http://blogs.sun.com/roller/page/theaquarium?entry=elvis_speaks_the_secret_of
>
>