Kabir, Related to the porting work, please have a look at https://github.com/bstansberry/jboss-as/tree/attributes If it looks good, I'll merge it into detyped2 in the morning. That's support for a "write-attribute" operation that can work for any attribute that has a handler registered. The operation takes 2 params: name -- the name of the attribute value -- the new value Resource descriptions will now include a new field for attributes called "access-type". It will have one of 3 values -- read-only, read-write, write-only. Those are generated by the registry; they don't need to be added by the DescriptorProvider. If it looks good, use of this mechanism should be the standard way to handle the simple "setFoo" type operations. People would write an OperationHandler to handle the operation, and call ModelNodeRegistration.register(ReadWrite|WriteOnly)Attribute("foo", handler). I'm sure we can write one or two abstract handlers (with an abstract method to validate the value) plus probably a few concrete ones for some basic common use cases (e.g. accept any non-null String value). OT: I noticed the global operations all have "request-properties" as part of the operation structure. That level should only be part of the operation's description, not part of the operation itself. On 1/17/11 3:54 PM, Emanuel Muckenhuber wrote: -- Brian Stansberry Principal Software Engineer JBoss by Red Hat

OK, I'll start off looking at logging and threads On 17 Jan 2011, at 21:54, Emanuel Muckenhuber wrote:

It would be good if we can try to complete a descriptive subsystem, that covers most of the use cases we have for the web-UI. JCA would be a good fit. If we can make sure that's covered first, it would be a great help. /Heiko On Jan 17, 2011, at 8:43 PM, Kabir Khan wrote:

On 21 Jan 2011, at 16:51, Kabir Khan wrote: It does not have operations to update individual attributes; for examples of that see GlobalOperationsTestCase.