Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Metamodel dependence on ServiceRegistry

Description

There are 2 options here:

  1. Metadata can take a ServiceRegistry as ctor param : new Metadata( serviceRegistry )

    1. this will be the short term solution

  2. serviceRegistry.getService( Metadata.class )

    1. possibly the long term solution

    2. pro/con: metadata lives on as part of SessionFactory (would continue to be available)

    3. possible first step to allowing "changes on the fly"

    4. maybe utilize internal caching (not our cache API) rather than simple maps to leverage disk storage capabilities of the cache (infinispan or ehcache)

Activity

Fixed

Details

Assignee

Reporter

Time tracking

0.57h logged

Components

Fix versions

Priority

Created April 11, 2011 at 6:41 PM
Updated April 12, 2011 at 1:10 AM
Resolved April 12, 2011 at 1:10 AM