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.
Difference between revisions of "EclipseLink/DesignDocs/Extensibility"
| Line 1: | Line 1: | ||
'''UNDER CONSTRUCTION''' | '''UNDER CONSTRUCTION''' | ||
| + | |||
| + | == 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 == | == Multi-tenancy discussion == | ||
Revision as of 16:25, 11 January 2011
UNDER CONSTRUCTION
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
Multi Tenant Features: Description of features available and being considered for Multi Tenant APPs