]
Steve Ebersole commented on HHH-6640:
-------------------------------------
Decided to utilize an optional additional contract
({{org.hibernate.integrator.spi.ServiceContributingIntegrator}}) for this.
Add ability for Integrator to prepare ServiceRegistryBuilder and
MetadataImplementor as part of lifecycle
---------------------------------------------------------------------------------------------------------
Key: HHH-6640
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6640
Project: Hibernate Core
Issue Type: Improvement
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 4.0.0.CR3
2 new, related capabilities:
# The ability for an {{org.hibernate.integrator.spi.Integrator}} to prepare the
{{org.hibernate.service.ServiceRegistryBuilder}}. The general idea here is to allow the
{{org.hibernate.integrator.spi.Integrator}} to add both prepared services
({{org.hibernate.service.ServiceRegistryBuilder#addService}}) and
({{org.hibernate.service.ServiceRegistryBuilder#addInitiator}}). An additional use case
could be to define alternate default settings via {{#applySetting}}, {{#applySettings}}
and {{#configure}}. This call will most likely occur from the
{{org.hibernate.service.ServiceRegistryBuilder}} constructor.
# The ability to prepare Metadata. One example is overriding {{Type}} registrations.
Both of these are "baselining" capabilities, meaning that they are defining
baselines which explicit user calls, user supplied metadata, etc might override any work
done here.
See the following 2 IRC discussions for origins/thoughts:
#
http://transcripts.jboss.org/channel/irc.freenode.org/%23hibernate-dev/20...
#
http://transcripts.jboss.org/channel/irc.freenode.org/%23hibernate-dev/20...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: