[
https://issues.jboss.org/browse/WFLY-4296?page=com.atlassian.jira.plugin....
]
Matt Fellows commented on WFLY-4296:
------------------------------------
+1 to the voice of those not wishing this to be deprecated.
"Currently only scenario where it kinda works ok is in standalone mode when you are
doing application developing."
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).
"And when you keep this in mind you can see that EE6+ feature
http://docs.oracle.com/javaee/7/api/javax/annotation/sql/DataSourceDefini... more
than satisfies it."
It does not cope with dynamic datasource definitions. 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 (At least as far as I can tell).
I'm sure I'm not in the majority of users with my crazy use case, but nevertheless
I'm also sure this is a very important feature to me. Editing the standalone.xml
during runtime is not sensible or particularly safe. Running a command via the CLI, is
possible, but feels a little icky to run Command Line scripts in Java code. Dropping a
templated -ds.xml file into the deployments folder feels safer to me.
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)