Tom Ware wrote:
> Hi Sahoo,
>
> The static weaving feature allows a preprocessing step to output files
> that have been weaved prior to deployment. This will allow LAZY OneToOne
> and ManyToOne mappings to act as though they are actually lazy in
> environments where dynamic weaving is not available. These files can
> then be included in the jar file containing your persistence unit and
> the dynamic weaving step that occurs at deployment can be avoided. The
> main reason for these changes is to allow users of non-J2EE 5 compliant
> containers to have LAZY loading available to them when using the
> persistence API.
>
> The feature is currently fairly rudimentary, and we are planning to do
> some more work to make it easier to use. The preprocessing step is done
> by running the main method in the StaticWeaver class with a set of
> arguments. The classes can then be included in a persistence unit.
> That persistence unit should include the property: toplink.weaving=static.
>
> Let me know if there is any more information you would like,
> Tom
I assume the resulting files are no longer portable, correct?
They'll only work when used with TopLink.