[
https://issues.apache.org/jira/browse/TAP5-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom van Dijk updated TAP5-1313:
-------------------------------
Comment: was deleted
(was: It appears I also need to add Dynamic contributions (basically, this
allows modules that create dynamic services to also contribute configurations
to them)
I'll get on it.
It also seems a ObjectLocator.getService(Class serviceImplementation, Class...
markers) is very useful.
I added both things, you can see the result on my git at
git://hetdiana.homeip.net/tapestry5.git (branches iocmod3 and hibmod))
> Configuration groups to easily allow multiple services with same
> implementation, allowing handling multiple hibernate databases
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1313
> URL: https://issues.apache.org/jira/browse/TAP5-1313
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-hibernate, tapestry-ioc
> Reporter: Tom van Dijk
> Attachments:
> Multiple-databases-support-using-configuration-group.patch
>
>
> Contribution groups allow service implementations that are closely linked
> together, to be created multiple times (using markers to identify them) with
> automatic dependency resolution.
> e.g. service implementations OneImpl (implements One) and TwoImpl (implements
> Two) use eachother, then with markers red and blue, we get One@Red and
> One@Blue and Two@Red and Two@Blue. They will each have their own
> configurations (unmarked contributions go to both Red and Blue, but
> contributions marked Red will go to the One@Red and Two@Red services, etc.)
> This is applied to the hibernate and hibernate-core services, allowing
> multiple databases to be used without having to use spring services.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
