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
Sanjeeb Kumar Sahoo wrote:
>Hi Tom,
>
>Tom Ware wrote:
>
>
>>Issue number: entity-persistence update
>>Obtained from: TopLink
>>Submitted by: Tom Ware
>>Reviewed by: TopLink Team
>>
>>-Glassfish Issue #595 - @IdClass is not working in an inheritance
>>hierarchy
>>-Glassfish Issue #632 - REGRESSION: access=FIELD in orm.xml is ignored
>>- defaults to PROPERTY
>>-Allow entity persistence to staticaly weave classes and make use of
>>those classes
>>
>>
>Would you mind telling a bit more on /static weaving/? What it does, how
>can it be used and why is it needed?
>
>Thanks,
>Sahoo
>
>
>>Tested with QuickLook, entity-persistence-tests, and Oracle-internal
>>tests
>>
>>Attached are diff files corresponding to transactions that made the
>>above changes. Note: We are currently discussing ways to provide more
>>detail about these transactions.
>>
>>