Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Search results
Create the page "EclipseLink/Examples/JPA/MetadataSource/" on this wiki! See also the search results found.
Page title matches
- MetadataSource was extended to support properties overrides. <property name="eclipselink.metadata-source" value="XML"/>2 KB (193 words) - 12:21, 11 April 2012
- = EclipseLink JPA MetadataSource = ...tomization including [[EclipseLink/Examples/JPA/Extensibility | Extensible JPA Entities]].3 KB (450 words) - 08:12, 13 June 2011
Page text matches
- 1. Design a standard JPA Application 5. To provide additional mappings, provide an eclipselink-orm.xml file that contains the additional mappings.16 KB (2,217 words) - 12:24, 11 January 2012
- The MySports example is a web application which demonstrates EclipseLink's latest features: * External Metadata: Using the JPA and JAXB MetadataSource capabilities the tenant specific extensions and mapping definitions are sto10 KB (1,390 words) - 13:54, 21 June 2012
- |eclipselink=y |eclipselinktype=JPA4 KB (564 words) - 09:30, 4 July 2011
- ...information, please see "JPA Entities and JAXB Beans Extensible" in the ''EclipseLink Solutions Guide'': http://www.eclipse.org/eclipselink/documentation/latest/solutions/extensible.htm14 KB (1,954 words) - 08:03, 17 April 2013
- = EclipseLink 2.4.0 Development Plans = This page is a working document for what is being planned and developed for EclipseLink 2.4.0, which is part of the Juno coordinated release shipping in June of 205 KB (654 words) - 23:37, 20 June 2012
- = EclipseLink JPA MetadataSource = ...tomization including [[EclipseLink/Examples/JPA/Extensibility | Extensible JPA Entities]].3 KB (450 words) - 08:12, 13 June 2011
- ...rrent information, please see "Using an External MetaData Source" in the ''EclipseLink Solutions Guide'': http://www.eclipse.org/eclipselink/documentation/latest/solutions/metadatasource.htm5 KB (609 words) - 08:05, 17 April 2013
- == Design document for adding JPA/JAXB metadata support to DBWS == ...n place of EclipseLink deployment XML. This feature is required to resolve EclipseLink [https://bugs.eclipse.org/bugs/show_bug.cgi?id=332227 Bug 332227].29 KB (3,496 words) - 13:00, 19 June 2013
- <p class=MsoTitle>Documentation Plan for EclipseLink 2.4</p> <p class=MsoNormal>[[Talk:EclipseLink/Development/Documentation/2.4|Added discussion page]]</p>38 KB (5,550 words) - 09:45, 12 January 2012
- ...currently offers a SINGLE_TABLE or VPD type, see [http://wiki.eclipse.org/EclipseLink/Development/Indigo/Multi-Tenancy Multitenant] === JPA Tenant Scope ===17 KB (2,358 words) - 22:44, 9 June 2012
- [[Category:EclipseLink/Example|MOXy Examples]] ...xamples are provided to assist developers with their adoption and usage of EclipseLink's JAXB and native OXM functionality.6 KB (802 words) - 05:28, 29 September 2015