[jboss-jira] [JBoss JIRA] (WFLY-2986) cli batch incorrect handling of the enabled attribute during datasource creation
[
https://issues.jboss.org/browse/WFLY-2986?page=com.atlassian.jira.plugin....
]
Stefano Maestri resolved WFLY-2986.
-----------------------------------
Resolution: Won't Fix
It's happening because adding a datasource w/ enabled==true is in fact creating a
composite operation in which second step is :enable and it's executed in Model.STAGE,
so after :disable operation of the batch.
After all is a non sense create a batch adding a datasource w/ enabled==true and the
:disable it in the same batch. Just create it w/ enabled==false.
So I'm closing this issue as won't fix
cli batch incorrect handling of the enabled attribute during
datasource creation
--------------------------------------------------------------------------------
Key: WFLY-2986
URL: https://issues.jboss.org/browse/WFLY-2986
Project: WildFly
Issue Type: Bug
Components: Domain Management, JCA
Affects Versions: 8.0.0.Final
Environment: win 7 pro sp2
wildfly 8.0.0.Final
Reporter: Gabriele Garuglieri
Assignee: Stefano Maestri
case:
/subsystem=datasources/data-source=xxxxxx:add(....) (without declaring enabled
attribute)
the ds is created with enabled=true, consistent with xsd default, but after WFLY-86
shouldn't it default to false when omitted ?
/subsystem=datasources/data-source=xxxxxx:add(...., enabled=true)
the ds is created with enabled=true as requested
but in both cases the operation
/subsystem=datasources/data-source=xxxxxx:disable
WITHIN THE SAME BATCH is happily ignored, ie the final outcome is success but the state
of the created ds is still enabled.
The opposite instead works, adding the ds with enabled=false produces a disabled ds and
adding
/subsystem=datasources/data-source=xxxxxx:enable
within the same batch, produces an enabled ds.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)