Issue Details (XML | Word | Printable)

Key: NUCCORE-192
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Andy Jefferson
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
DataNucleus Core

Remove MetaDataManager from Metadata objects so they are independent of where they are being used

Created: 16/Feb/09 08:10 AM   Updated: 19/Apr/10 09:57 AM
Component/s: MetaData
Affects Version/s: None
Fix Version/s: None


 Description  « Hide
With the new JDO 2.3 metadata API it would be convenient to be able to define some metadata, and then use it for enhancement and also for runtime. We currently cannot do this since the metadata, once populated, is tied to a metadata manager

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 24/Jul/09 08:26 AM
Majority of this is now complete. The remaining part is in the AbstractMemberMetaData.setRelation(). Maybe this ought to be done in initialize ?

Andy Jefferson added a comment - 17/Dec/09 05:35 PM
Code is now pretty much isolated into
AbstractMemberMetaData.setRelation()
FileMetaData.setMetaDataManager()

Tried adding a postInitialise() method, but maybe need to play around with where it is called from. Just doing it when reading in a FileMetaData resulted in a StackOverflow for persistent interfaces (test.jdo.datastore PersistentInterfacesTest).

Once this is done then can get rid of ClassLoaderResolver argument to several methods in AbstractMemberMetaData.