Re: [jbosstools-dev] Questions about new JMX/AS integration
by Max Rydahl Andersen
>>> The filter works on the MBean's ObjectName.
>>> Typing "name" will match any MBeans which has a property with a "name"
>>> key (and a lot of MBeans will match!).
>>> The MBean Explorer display only the values of the ObjectName
>>> properties (as nodes of its tree). To make it consistent with the UI,
>>> a refinement could be to filter only on the ObjectName properties
>>> values (and not their keys).
>> What confuses me is that I can't see in the ui for all matched items
>> someting that includes "name" which is what I would expect when typing
>> a filter onto a tree...right ?
>
> The MBean Explorer tree tells only half of the story, it displays the
> property values but not the keys.
> For example, the MBeans associated to "foo:type=Bar,name=Alice" &
> "foo:type=Bar,name=Bob" will be displayed in the tree as
>
> - foo
> - Bar
> - Alice
> - Bob
>
>
> UI-wise, you can not know from the tree that "Bar" corresponds to the
> "type" property and "Alice" to the "name" property.
> In practice, it is rarely a problem as long as the ObjectNames are
> constructed using JMX best practices[1].
Well, in this example I can see that both Alice and Bob is related to type
Bar.
But there is something else flakey about it. See
http://screencast.com/t/Sdtbv0HA
Sometimes the results is not expanded. Sometime typing the same query
gives different
result (looks like the previous filter affects the new result ?)
> I see 2 options there:
> #1 - keep the tree as it is and filters only on the visible parts of the
> ObjectNames (i.e. the domain & the properties' values)
I think this makes sense.
> #2 - display the properties keys in the tree and filter on the full
> ObjectName:
>
> - foo
> - type=Bar
> - name=Alice
> - name=Bob
Too verbose...
>>> yes, the filter is case sensitive.
>> Shouldn't it be case insensitive ?
>> Any usecase for it not being ?
>
> I like my search to be case-sensitive by default :)
>
> But, you're right, the filter would be me more user-friendly if case
> insensitive.
:)
--
/max
15 years, 5 months
Re: [jbosstools-dev] Questions about new JMX/AS integration
by Max Rydahl Andersen
>>> My question is about the filter field in the JMX tree.
>>> What does this field actually filter on ? i.e. if I enter "name" it
>>> shows me alot of nodes which does not seem to have "name" in them.
>
> The filter works on the MBean's ObjectName.
> Typing "name" will match any MBeans which has a property with a "name"
> key (and a lot of MBeans will match!).
> The MBean Explorer display only the values of the ObjectName properties
> (as nodes of its tree). To make it consistent with the UI, a refinement
> could be to filter only on the ObjectName properties values (and not
> their keys).
What confuses me is that I can't see in the ui for all matched items
someting that includes "name" which is what I would expect when typing
a filter onto a tree...right ?
>>> And is it intentional the search is casesensitive ? (I for one cannot
>>> figure out the random camel casing in JMX names ;)
>
> yes, the filter is case sensitive.
Shouldn't it be case insensitive ?
Any usecase for it not being ?
>>> In the tree is double click not supposed to do something when I click
>>> on operations ? i.e. open the editor and have that property/method
>>> selected ready for execution ?
>
> Normally, double-click on a operation in the MBean explorer must open
> the corresponding MBean editor and select the given operation.
> This issues appeared when the implementation switched to using the
> Common Navigator.
ok - so that is a regression we need fixed.
--
/max
15 years, 5 months
Questions about new JMX/AS integration
by Max Rydahl Andersen
Hi,
I saw https://jira.jboss.org/jira/browse/JBIDE-2760 was fixed and I must
say this is a *great* improvement over our embedded simple JMX tree.
It is great that I don't have to configure the configured AS's but would
be good if the JMX view would give some indication I need to start the
server in the Server view to expand the node (yes - I'm Mr. Stupid User)
I've created a few other issues I bumped into in the JMX component, but
also got a few questions on how the JMX functionallity is supposed to work
;)
(you can see the jmx issues here:
https://jira.jboss.org/jira/browse/JBIDE/component/12312059)
My question is about the filter field in the JMX tree.
What does this field actually filter on ? i.e. if I enter "name" it shows
me alot of nodes which does not seem to have "name" in them.
And is it intentional the search is casesensitive ? (I for one cannot
figure out the random camel casing in JMX names ;)
In the tree is double click not supposed to do something when I click on
operations ? i.e. open the editor and have that property/method selected
ready for execution ?
----
/max
15 years, 5 months
