[
https://issues.apache.org/jira/browse/TAPESTRY-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622567#action_12622567
]
Jonathan Barker commented on TAPESTRY-2582:
-------------------------------------------
I'm using Spring, and in about a third of what I do, I need multiple
connections. It's one of the reasons I have not been motivated to move away
from Spring.
Some cases could be handled with specification of schema and catalog to use
multiple databases within the same server on the same Session; others are on
different servers with different database engines.
There is usually one primary DB that I want to configure with as little effort
as possible, and the corresponding SessionFactory gets autowired into my DAO's.
The other SessionFactory(s) I specify are not for autowiring so I don't get
grumbling about multiple SessionFactories.
It would be good to have "First Class" support for this functionality.
> Let Tapestry - Hibernate connect to multiple databases
> ------------------------------------------------------
>
> Key: TAPESTRY-2582
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2582
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10,
> 5.0.11, 5.0.12, 5.0.13, 5.0.14
> Environment: All
> Reporter: Ernest Monklitch
> Fix For: 5.0.15
>
>
> Tapestry - Hibernate integration should include mechanism to connect to
> multiple databases via named sessions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
