This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 339371 - Extensibility Feature Set (MOXy)
Summary: Extensibility Feature Set (MOXy)
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL: http://wiki.eclipse.org/EclipseLink/D...
Whiteboard:
Keywords:
Depends on: 335601 45328 339373 339377 339381 339383 345328
Blocks:
  Show dependency tree
 
Reported: 2011-03-09 10:28 EST by Blaise Doughan CLA
Modified: 2022-06-09 10:06 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Blaise Doughan CLA 2011-03-09 10:28:33 EST 
The goal of this feature is to allow a user to start with a predesigned
JAXBContext and add mappings to the entities in that context
without the need for the context to be recreated. 

Static extensions defined for the extensible entity types prior to the
application starting. 

Dynamic are extensions defined while the application is operating. 
The set of features we build for Extensible Entity Types will provide a
foundation that can be build on by users that want to build multi-tenant
applications can specify tenant specific extensions. 

See web page above for more details.

This ER will be the main ER for the feature set.  Each feature we add based on
the extensibility requirements will also have a separate ER that will be listed
in this bug.
Comment 1 Rick Barkhouse CLA 2011-05-16 10:51:58 EDT 
Feature complete for 2.3
Comment 2 Eclipse Webmaster CLA 2022-06-09 10:06:24 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink