Re: [eclipselink-users] programmatic customization of mapping meta-data

[Tom Ware <tom.ware@xxxxxxxxxx>]

Hi Olaf,

  What kinds of things do you want to do in your meta-data modification?

  Depending on what you want to do, there may be several ways to make 
modifications to the metadata.

1. There is a Customization mechanism that allows you to customize the mappings 
that are created by our meta-data processing
2. There is an event mechanism the provides you with callbacks at certain stages 
of our initialization
3. You can specify your mappings in XML. (with the option of having the XML be 
the only source of mappings)

  You should also be aware that some performance features in EclipseLink are 
enabled by byte-code weaving.

-Tom

Olaf Otto wrote:
> Hello eclipse users!
>
> I have a framework that makes massive use of aspect-oriented programming 
> and code generation. This includes a significant amount of additional 
> fields being created in various classes (of a project using the 
> framework, not in the framework itself) by a java agent at class loading 
> time.  These fields are primarily generated for internal framework 
> purposes and are thus invisible to a framework user.
>
> Most of these fields are references to non-serializable resp. custom 
> types and must be handled in a non-standard fashion for persistence.
>
> Now here is the question: Is there a way to hook into the meta-data 
> processing occurring during predeployment? More precisely, i would like 
> to access and modify the persistence meta-data of entities before 
> processor.processORMMetadata() is invoked in the processORMetadata of 
> the PersistenceUnitProcessor class.
>
> Thank you and regards,
> Olaf
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users