[
https://issues.apache.org/jira/browse/TAP5-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1313:
---------------------------------
This issue has been last updated about 1.5 years ago and has no information
about the versions that are affected. That makes it hard to determine whether
it is still relevant.
If the issue still persists with the current stable version (5.3.7) or the most
recent development preview of Tapestry (5.4-beta-6), both of which are
available from Maven Central, please update it as soon as possible, adding the
respective version(s) to the issue's "Affects Version/s".
> 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 was sent by Atlassian JIRA
(v6.2#6252)
