Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] Bug 211330 - Add attributes-complete support to the EclipseLink-ORM.XML Schema

Hi Shaun,
What we want to do is avoid processing the class for mapping defaults. Current deployment XML users specify their complete set of mappings within the XML file with no notion of EclipseLink inspecting those files for other 'default' mappings. Migrating these users to the new format (and metadata processing) we need to ensure there is a way to preserve this.
Currently, specify an xml-mapping-metadata-complete falls a little short of this functionality since it will use those mappings that are in XML and ignore annotations, however, the processing will still inspect the class for default mappings for basics, 1-1's, 1-M's and Variable1-1's.
Bug 218082 (conversion tool, current deployment XML -> new Eclipselink orm schema format) also depends on a solution to this bug.
----- Original Message -----
Sent: Wednesday, May 21, 2008 9:32 AM
Subject: Re: [eclipselink-dev] Bug 211330 - Add attributes-complete support to the EclipseLink-ORM.XML Schema

Hi Guy,

   Can you elaborate on the problem? Your initial description is:
Which is a flag to indicate not to auto-generate any unspecified attributes. This is important in XML when the class may continue to evolve.
When  you say "auto-generate" are you talking about DDL generation?  Can you provide an example of the issue?


Guy Pelletier wrote:
Two suggestions to address the following bug have been documented.

Please review and provide any feedback.

eclipselink-dev mailing list


Shaun Smith | Principal Product Manager, TopLink | +1.905.502.3094
Oracle Fusion Middleware
110 Matheson Boulevard West, Suite 100
Mississauga, Ontario, Canada L5R 3P4

GIF image

Back to the top