This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 339383 - Enhancement: Persist metadata modifications made at runtime
Summary: Enhancement: Persist metadata modifications made at runtime
Status: CLOSED WONTFIX
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: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 339373 339377
Blocks: 339371
  Show dependency tree
 
Reported: 2011-03-09 11:10 EST by Blaise Doughan CLA
Modified: 2022-06-09 10:29 EDT (History)
0 users

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 11:10:45 EST 
Once the ability is added to make metadata modifications at runtime, MOXy will need to ability to persist the metadata in some form (oxm.xml, other representation?).  This is so that if the JAXBContext is part of an application that the metadata can survive the application being restarted.
Comment 1 Blaise Doughan CLA 2011-05-02 11:37:53 EDT 
Instead of changes being made at runtime that need to be persisted, changes will be made externally and the JAXBContext will be refreshed:

Bug 343615 - Enhancement: Add ability to refresh JAXBContext based on metadata changes
https://bugs.eclipse.org/343615
Comment 2 Eclipse Webmaster CLA 2022-06-09 10:29:12 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink