[
https://issues.jboss.org/browse/AS7-1381?page=com.atlassian.jira.plugin.s...
]
Heiko Braun edited comment on AS7-1381 at 7/27/11 5:27 AM:
-----------------------------------------------------------
Take an example RA config:
{noformat}
"result" => {
"archive" => "xmpp-ra.rar",
"background-validation" => undefined,
"background-validation-minutes" => undefined,
"blocking-timeout-wait-millis" => undefined,
"config-properties" => [
("host" => "talk.google.com"),
("port" => "5222")
],
"connection-definitions" => [{
"class-name" =>
"com.ramphastos.xmpp.XmppConnectionFactory",
"jndi-name" => "java:jboss/eis/xmpp",
"pool-name" => "xmpp-ra_rar-Pool"
}],
"idle-timeout-minutes" => undefined,
"max-pool-size" => undefined,
"min-pool-size" => undefined,
"pool-prefill" => undefined,
"pool-use-strict-min" => undefined,
"transaction-support" => "NoTransaction",
"use-fast-fail" => undefined
}
{noformat}
I cannot update "connection-definitions" or "config-properties"
through the management API, because they are not addressable. System properties are a good
example how it should be done to prevent this problem:
{noformat}
[standalone@localhost:9999 /] /host=master:read-resource
{
"outcome" => "success",
"result" => {
"domain-controller" => {"local" => {}},
"extension" => undefined,
"name" => "master",
"namespaces" => [],
"path" => undefined,
"schema-locations" => [],
"core-service" => {"management" => undefined},
"interface" => {
"public" => undefined,
"management" => undefined
},
"jvm" => {"default" => undefined},
"server" => {
"server-one" => undefined,
"server-two" => undefined
},
"server-config" => {
"server-one" => undefined,
"server-two" => undefined,
"server-three" => undefined
},
"system-property" => {
"propertyTwo" => undefined,
"porpertyOne" => undefined
}
}
}
{noformat}
As you can see the system-properties are sub resources (property lists) that can be
addressed and thus modified on their own:
{noformat}
// read
[standalone@localhost:9999 /] /host=master/system-property=propertyTwo:read-resource
{
"outcome" => "success",
"result" => {
"boot-time" => false,
"value" => "twoValue"
}
}
// remove
[standalone@localhost:9999 /] /host=master/system-property=propertyTwo:remove
// write
[standalone@localhost:9999 /] /host=master/system-property=someProp:add(value=test)
{noformat}
was (Author: heiko.braun):
Take an example RA config:
{noformat}
"result" => {
"archive" => "xmpp-ra.rar",
"background-validation" => undefined,
"background-validation-minutes" => undefined,
"blocking-timeout-wait-millis" => undefined,
"config-properties" => [
("host" => "talk.google.com"),
("port" => "5222")
],
"connection-definitions" => [{
"class-name" =>
"com.ramphastos.xmpp.XmppConnectionFactory",
"jndi-name" => "java:jboss/eis/xmpp",
"pool-name" => "xmpp-ra_rar-Pool"
}],
"idle-timeout-minutes" => undefined,
"max-pool-size" => undefined,
"min-pool-size" => undefined,
"pool-prefill" => undefined,
"pool-use-strict-min" => undefined,
"transaction-support" => "NoTransaction",
"use-fast-fail" => undefined
}
{noformat}
I cannot update "connection-definitions" or "config-properties"
through the management API, because they are not addressable. System properties are a good
example how it should be done to prevent this problem:
{noformat}
[standalone@localhost:9999 /] /host=master:read-resource
{
"outcome" => "success",
"result" => {
"domain-controller" => {"local" => {}},
"extension" => undefined,
"name" => "master",
"namespaces" => [],
"path" => undefined,
"schema-locations" => [],
"core-service" => {"management" => undefined},
"interface" => {
"public" => undefined,
"management" => undefined
},
"jvm" => {"default" => undefined},
"server" => {
"server-one" => undefined,
"server-two" => undefined
},
"server-config" => {
"server-one" => undefined,
"server-two" => undefined,
"server-three" => undefined
},
"system-property" => {
"propertyTwo" => undefined,
"porpertyOne" => undefined
}
}
}
{noformat}
As you can see the system-properties are sub resources (property lists) that can be
addressed and thus modified on their own:
{norformat}
// read
[standalone@localhost:9999 /] /host=master/system-property=propertyTwo:read-resource
{
"outcome" => "success",
"result" => {
"boot-time" => false,
"value" => "twoValue"
}
}
// remove
[standalone@localhost:9999 /] /host=master/system-property=propertyTwo:remove
// write
[standalone@localhost:9999 /] /host=master/system-property=someProp:add(value=test)
{noformat}
Make RA config properties sub resources
---------------------------------------
Key: AS7-1381
URL:
https://issues.jboss.org/browse/AS7-1381
Project: Application Server 7
Issue Type: Feature Request
Components: JCA
Reporter: Heiko Braun
Assignee: Jeff Zhang
Fix For: 7.1.0.CR1
Take a look how system properties are represented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira