[
https://issues.jboss.org/browse/WFLY-4296?page=com.atlassian.jira.plugin....
]
arjan tijms commented on WFLY-4296:
-----------------------------------
{quote}I'd much prefer for this to be fixed so that deploying a -ds.xml file in the
deployments folder does indeed deploy this as a new datasource, (I'm fine with this
only working in standalone mode by the way).{quote}
You can basically still do that with the standard {{data-source}} element (or the
annotation if you so prefer). Just deploy a war with only the data source definition (use
{{java:global}}) independently from the application that uses that data source. This is
largely like you'd do with the deployment of a {{-ds.xml}} file.
{quote}Multitennanted systems which rely on database partitioning (Different database per
tennant), and thus require a specific datasource per tennant, decided at runtime, would
not be possible if this feature is deprecated{quote}
Which feature of {{-ds.xml}} is that exactly? If you're missing specific features then
it may be an idea to ask Red Hat to add those (via properties) to the standard
{{data-source}} one. There are indeed a (large) number of pool settings that JBoss/WildFly
doesn't wire from the properties. I studied the source and it looks relatively easy to
do it, it's just that it isn't done.
Another avenue is asking for standardisation of features for Java EE 8's
{{data-source}}. This would mean writing a mail to the Java EE mailing list at
users(a)javaee-spec.java.net
remove _ds.xml deployment support
---------------------------------
Key: WFLY-4296
URL:
https://issues.jboss.org/browse/WFLY-4296
Project: WildFly
Issue Type: Feature Request
Components: JCA
Reporter: Stefano Maestri
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)