[
https://issues.jboss.org/browse/WFLY-12121?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-12121:
-----------------------------------------
Back from PTO. Yes [~ochaloup] you would need to handle that manually and not use
setRequires.
The downside (besides more code) is the read-resource-description metadata won't
include that bit of info, but you can add it to the free form text description of the
attribute.
The tricky thing with manually validating is you need to add a step to do it; don't do
it directly. So OperationContext.addStep(...). That ensures that if config changes are
made in a composite/batch the other steps in the batch can run and you validate the end
result, not some intermediate state.
Transaction JDBC object store CLI operation fails when set to false
with information JDBC connection is needed
--------------------------------------------------------------------------------------------------------------
Key: WFLY-12121
URL:
https://issues.jboss.org/browse/WFLY-12121
Project: WildFly
Issue Type: Bug
Components: Transactions
Reporter: Ondrej Chaloupka
Assignee: Ondrej Chaloupka
Priority: Minor
If the JDBC store is for to be disabled it's needed to be used CLI command
{code}
/subsystem=transactions:write-attribute(name=use-jdbc-store, value=false)
{code}
(see documentation
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...)
but when a data source is not configured then even when it's to be set to false there
is an error that such operation is not possible
{code}
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0380: Attribute
'jdbc-store-datasource' needs to be set or passed before attribute
'use-jdbc-store' can be correctly set",
"rolled-back" => true
}
{code}
I would expect that when I want to disable the jdbc store I don't need to provide a
data source for a connection before. Setting-up the {{false}} should not throw an error in
CLI.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)