[jboss-jira] [JBoss JIRA] (AS7-6154) Expression support inconsistency
Heiko Braun (JIRA)
jira-events at lists.jboss.org
Thu Dec 13 02:55:17 EST 2012
[ https://issues.jboss.org/browse/AS7-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Heiko Braun updated AS7-6154:
-----------------------------
Description:
Although some subsystem declare support for expression on certain attributes, they actually don't support it.
As en example see datasources > pool > max-pool-size.
The DMR description says it supports expressions on this attribute:
{noformat}
"max-pool-size" => {
"type" => INT,
"description" => "The max-pool-size element specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool",
"expressions-allowed" => true,
"nillable" => true,
"default" => 20,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
{noformat}
But then writing an expression value yields an exception
{noformat}
Request
[ERROR] {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "steps" => [{
[ERROR] "address" => [
[ERROR] ("profile" => "full"),
[ERROR] ("subsystem" => "datasources"),
[ERROR] ("data-source" => "ExampleDS")
[ERROR] ],
[ERROR] "operation" => "write-attribute",
[ERROR] "name" => "max-pool-size",
[ERROR] "value" => expression "${pool:15}"
[ERROR] }]
[ERROR] }
{noformat}
{noformat}
08:48:23,965 DEBUG [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 5) JBAS014616: Operation ("write-attribute") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "ExampleDS")
]) - failure description: "JBAS014688: Wrong type for value. Expected [INT] but was EXPRESSION"
{noformat}
was:
Although some subsystem declare support for expression on certain attributes, they actually don't support it.
As en example see datasources > pool > max-pool-size.
The DMR description says it supports expressions on this attribute:
{noformat}
"max-pool-size" => {
"type" => INT,
"description" => "The max-pool-size element specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool",
"expressions-allowed" => true,
"nillable" => true,
"default" => 20,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
{noformat}
But then writing an expression value yields an exception
{noformat}
Request
[ERROR] {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "steps" => [{
[ERROR] "address" => [
[ERROR] ("profile" => "full"),
[ERROR] ("subsystem" => "datasources"),
[ERROR] ("data-source" => "ExampleDS")
[ERROR] ],
[ERROR] "operation" => "write-attribute",
[ERROR] "name" => "max-pool-size",
[ERROR] "value" => expression "${pool:15}"
[ERROR] }]
[ERROR] }
{noformat}
{noformat}
08:48:23,965 DEBUG [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 5) JBAS014616: Operation ("write-attribute") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "ExampleDS")
]) - failure description: "JBAS014688: Wrong type for value. Expected [INT] but was EXPRESSION"
{noformat}
> Expression support inconsistency
> --------------------------------
>
> Key: AS7-6154
> URL: https://issues.jboss.org/browse/AS7-6154
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Brian Stansberry
> Fix For: 7.2.0.CR1
>
>
> Although some subsystem declare support for expression on certain attributes, they actually don't support it.
> As en example see datasources > pool > max-pool-size.
> The DMR description says it supports expressions on this attribute:
> {noformat}
> "max-pool-size" => {
> "type" => INT,
> "description" => "The max-pool-size element specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => 20,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> {noformat}
> But then writing an expression value yields an exception
> {noformat}
> Request
> [ERROR] {
> [ERROR] "operation" => "composite",
> [ERROR] "address" => [],
> [ERROR] "steps" => [{
> [ERROR] "address" => [
> [ERROR] ("profile" => "full"),
> [ERROR] ("subsystem" => "datasources"),
> [ERROR] ("data-source" => "ExampleDS")
> [ERROR] ],
> [ERROR] "operation" => "write-attribute",
> [ERROR] "name" => "max-pool-size",
> [ERROR] "value" => expression "${pool:15}"
> [ERROR] }]
> [ERROR] }
> {noformat}
> {noformat}
> 08:48:23,965 DEBUG [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 5) JBAS014616: Operation ("write-attribute") failed - address: ([
> ("subsystem" => "datasources"),
> ("data-source" => "ExampleDS")
> ]) - failure description: "JBAS014688: Wrong type for value. Expected [INT] but was EXPRESSION"
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list