We're updating the issue view to help you get more done. 

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)

Environment

None

Status

Assignee

Steve Ebersole

Reporter

Steve Ebersole

Components

Fix versions

Affects versions

4.0.0.Alpha2

Priority

Major