phase 1 : the design goal here is to limit class-loading and access to environmental resources which might not yet be available (datasources, jndi,etc)
build BootstrapServiceRegistry - this step is sort of optional and only really needed if user wants to:
override how class-loading works
supply explicit "provided" Integrator instances
override how "strategy selection" works (although can also be done via Java ServiceLoader resolution).
build MetadataSources - this collects the sources of mapping information (HBM files, annotated classes, etc).
phase 2 : at this stage we assume the limits imposed on phase 1 are no longer applicable
build StandardServiceRegistry
build Metadata
use StandardServiceRegistry and Metadata to build SessionFactory
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Design: