Deployed -ds.xml not shown in 'subsystem=datasource'

[dastraub]

With 7.1.0.Final the deployment of datasources via  -ds.xml files comes back, thanks !

This datasources are still available, but not shown in the JBoss admin console or available with the cli.

[hallvard.lid]

We have the same issue with JMS-queues, is it possible to get it both ways somehow - deploy these resources with the application and get them visible in the admin console? I find the deployed jms-resources under something called deployment=test-jms.xml, inside that tree i get the subsystem=messaging and the hierarchy that matches the "global" subsystem=messaging.

If it is possible through the xml to just force the datasource/jms-queue into the correct tree - then we would get the datasources/queues in the admin-gui

This is not meant as a hijacking of this thread, but the *-ds.xml-deployment-method seems to be excactly the same as the *-jms.xml method.

Hallvard

[jbertram]

Using a *-ds.xml is possible for flexibility with older management paradigms, but not exactly recommended.  The trade-off with using the *-ds.xml is that it is no longer managed the way "normal" datasources (e.g. which are deployed in standalone*.xml) are managed.  To my knowledge, any datasource in *-ds.xml will not be available via the JBoss Admin Console or the CLI.  Furthermore, there are currently no plans to add this functionality.

[dastraub]

You're right, this is also mentioned in https://docs.jboss.org/author/display/AS71/DataSource+configuration.

Unfortunately I haven't read it carefully ...

I guess the use case for -ds.xml files is more for providing e.g. connection settings for resource adapters.

[wdfink]

Mark with '!' (makro) as a better visible warning