[ https://issues.jboss.org/browse/AS7-1381?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen commented on AS7-1381: -------------------------------------- What "attributes" ? If you mean the resource adapter config-property's, then they are only writeable if the resource adapter is version 1.6, and supports dynamic updates. That should already be supported. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1381?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-1381: ---------------------------------- 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 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} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1381?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-1381: ---------------------------------- See also: - http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/003315.html - http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/003350.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1381?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-1381: ----------------------------- Priority: Blocker (was: Major) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1381?page=com.atlassian.jira.plugin.s... ] Stefano Maestri updated AS7-1381: --------------------------------- Fix Version/s: 7.1.0.Beta1 (was: 7.1.0.CR1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1381?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-1381: ----------------------------- Forum Reference: http://community.jboss.org/thread/172645 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1381?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy commented on AS7-1381: ----------------------------------- Please note that enabling to add connection-factory as part resource-adapter is only half solution. We should be able to add/remove/modify a connection-factory to a existing resource-adapter. So, achieve that connection-factory should be designed as a "sub-model" under the "resource-adapter" model. The current operations like "flush-xxx" needs to be moved to this connection-factory sub-model level. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1381?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy commented on AS7-1381: ----------------------------------- Based on request http://community.jboss.org/thread/172323 when you design the connection factories can you deploy them as individual services, with JNDI name in service name. Having them as services makes it very useful to tie them as dependencies to other down stream services. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira