[
https://issues.apache.org/jira/browse/KARAF-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216265#comment-14216265
]
Benjamin Graf commented on KARAF-3035:
--------------------------------------
Hi Christinan,
JIRA ticket is created (https://ops4j1.jira.com/browse/PAXJDBC-49)
I like the idea with the directory with the name of the factory id. I think
should a feature could be useful in different scenarios.
Well, if you have a integration platform with several databases and data
sources bound, you'll face many difficulties like maintenance, db crashes,
exception causing statements... The question is how you can react to those
scenarios. Unbound datasource instance for maintenance (deactivate not delete)?
How will Service/bundle react on exceptions? Actually all datasources are bound
to its own blueprint file => osgi bundle. There separately stoppable and don't
interact with each other. If creating datasources over pax-jdbc-config there
exists only one owner who exports the osgi datasource services. How will this
bundle react if services are failing?
Benjamin
> Use aries transaction jdbc / jms for pooling
> --------------------------------------------
>
> Key: KARAF-3035
> URL: https://issues.apache.org/jira/browse/KARAF-3035
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 4.0.0
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: 4.0.0, 3.0.3, 2.4.1
>
> Attachments: templates.zip, vcs-diff1271163984438294153.patch,
> vcs-diff4588490555533395514.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
