[
https://issues.jboss.org/browse/WFLY-5584?page=com.atlassian.jira.plugin....
]
Stefano Maestri commented on WFLY-5584:
---------------------------------------
BTW WFLY-5426 should solve problem w/ DEFAULT profile.
DEFAULT profile is there exactly to be able to get -ds.xml deployed driver from
_installed-driver-list and for standalone configuration.
As Harald spotted in PR the concept is used from web console and can't be removed.
I suggested to close this issue and eventually open one describing the effective problem
with the use case not working w/ current implementation
Remove and deprecate profile concept for data-sources
-----------------------------------------------------
Key: WFLY-5584
URL:
https://issues.jboss.org/browse/WFLY-5584
Project: WildFly
Issue Type: Bug
Components: JCA
Reporter: James Perkins
Assignee: James Perkins
Priority: Blocker
Fix For: 10.0.0.Final
The datasource subsystem was given the concept of domain profiles in WFLY-3634. This
doesn't appear to have been fully implemented as {{-ds.xml}} deployments in domain
mode don't work. During the deploy process the profile is passed as {{null}} which
results in the profile named {{default}} being used. Essentially this means that
{{-ds.xml}} domain deployments would only ever work on a profile named {{default}}.
While debugging the issue it doesn't seem as if the profile concept is even needed
for data sources. The subsystem is only registered on servers and a server shouldn't
need to know about profiles.
In short the profile concept needs to be removed and the {{profile}} attribute on the
result of the {{installed-drivers-list}} operation as well as the {{installed-drivers}}
complex attribute needs to be deprecated. The attribute was added for the web console and
per
https://developer.jboss.org/message/941413#941413 it is not used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)