[jboss-as7-dev] Console Feedback

[Brian Stansberry]

On 4/12/11 11:46 AM, Heiko Braun wrote:
>
> On Apr 12, 2011, at 4:27 PM, Jim Tyrrell wrote:
>
>> My thought would be:
>>
>> If there are 10-20 items probably an alphabetized list.
>>
>> If you do categories as talked about below, a search feature should be
>> available like the new in Eclipse to quickly drill into the sub groups
>> to find your section. ie ones integration is another persons core..ie
>> I could see a datasource being in both, until I "know" where it is.
>>
>
> that's something we can consider.
>
>
>> Do you envision this list being customer modifiable ala the JMX
>> console, in that any arbitrary JMX like bean or whatever we call it
>> can be loaded?
>>
>
> not directly. there will however be the ability to disable subsystems.
> in that case they will not show up. but it's a general management use
> case available
> across API entrypoints and not specific to the console.
>

We have an Extension SPI, which includes the ability to register new 
subsystems. The core management API includes operations to add new 
extensions and to add the subsystems they expose.

An arbitrary JMX MBean is not an Extension though; the SPI is much more 
complex than that. You can deploy mbean services into JBoss AS and have 
your application interact with them, but their details are not exposed 
via the core management API. They can be accessed via JMX of course, but 
we don't persist changes etc.

The other thing is an extension is not a deployment. Their code has to 
be packaged as JBoss Modules module and must be present in the path the 
AS uses for finding modules (i.e. in the modules/ dir.)


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat