Datasource attribute "enabled" not writable ------------------------------------------- Key: JBAS-9341 URL: https://issues.jboss.org/browse/JBAS-9341 Project: JBoss Application Server Issue Type: Bug Security Level: Public(Everyone can see) Components: JCA service Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.0.0.Beta4 [localhost:9999 /] /profile=default/subsystem=datasources/data-source=myDS:write-attribute(name=enabled, value=false) { "outcome" => "failed", "result" => {"domain-failure-description" => "Attribute enabled is not writeable"} }

Datasource attribute "enabled" not writable ------------------------------------------- Key: JBAS-9341 URL: https://issues.jboss.org/browse/JBAS-9341 Project: JBoss Application Server Issue Type: Bug Security Level: Public(Everyone can see) Components: JCA service Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.0.0.Beta4 [localhost:9999 /] /profile=default/subsystem=datasources/data-source=myDS:write-attribute(name=enabled, value=false) { "outcome" => "failed", "result" => {"domain-failure-description" => "Attribute enabled is not writeable"} }

> On 4/21/11 3:01 AM, Heiko Braun wrote: > >> > >> Both variants are fine. I can also understand the attempt to > >> distinguish operation vs attribute use cases. > >> > >> IMO this reveals one of the weak sports in the detyped API: > >> runtime vs. configuration properties of the system. > >> > >> to further distinguish these two I would suggest the following, > >> which may apply to other subsystems as well: > >> > >> - if changing the configuration impacts the runtime state (i.e. enabled->disabled) > >> then make it an operation > >> - if it's merely configuration then make it an attribute > >> > I'm fine with this, but let's clarify what "impacts the runtime state" > means. Many configuration changes will impact the runtime state. Instead > of "impacts the runtime state" I'd say "results in an MSC service > starting or stopping." That's the main case where an action has rippling > effects the user might not anticipate >

Datasource attribute "enabled" not writable ------------------------------------------- Key: AS7-187 URL: https://issues.jboss.org/browse/AS7-187 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.0.0.CR1 [localhost:9999 /] /profile=default/subsystem=datasources/data-source=myDS:write-attribute(name=enabled, value=false) { "outcome" => "failed", "result" => {"domain-failure-description" => "Attribute enabled is not writeable"} }

Datasource attribute "enabled" not writable ------------------------------------------- Key: AS7-187 URL: https://issues.jboss.org/browse/AS7-187 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 [localhost:9999 /] /profile=default/subsystem=datasources/data-source=myDS:write-attribute(name=enabled, value=false) { "outcome" => "failed", "result" => {"domain-failure-description" => "Attribute enabled is not writeable"} }