Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/DesignDocs/Extensibility"

(Replacing page with 'Contents moved to [http://wiki.eclipse.org/EclipseLink/DesignDocs/335601 ER 335601]')
 
(60 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''UNDER CONSTRUCTION'''
+
Contents moved to [http://wiki.eclipse.org/EclipseLink/DesignDocs/335601 ER 335601]
 
+
== Extensibility ==
+
 
+
The goal of this feature is to allow a user to start with a predesigned persistence unit and extend the entities in that persistence units with new mappings at runtime.
+
 
+
For example, a simple application is provided that defines a Customer entity that maps  "name" and "customer number". As the application is running, the Customer application can be extended to include a "company name" mapping.
+
 
+
In the above example, the addition of the "company name" is acheived only through interaction with EclipseLink.  EclipseLink should handle schema modifications (if any) and fixing the mapping.
+
 
+
== Multi-tenancy discussion ==
+
 
+
The following multi-tenancy discussion was used in the discussion of this feature
+
 
+
[[EclipseLink/DesignDocs/MultiTenantFeatures|Multi Tenant Features: Description of features available and being considered for Multi Tenant APPs]]
+

Latest revision as of 10:23, 16 March 2011

Contents moved to ER 335601

Back to the top