[
https://issues.apache.org/jira/browse/DELTASPIKE-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963966#comment-14963966
]
Romain Manni-Bucau commented on DELTASPIKE-1008:
------------------------------------------------
Hi Falko,
wonder if we shouldnt go for a objectName() method and deprecate category. If
Not we should support properties():
{code}
@MBean(category = "com.company.mbeans", properties = { "type=custom",
"j2eeType=myApp", "name=counter" })
{code}
(I have no big preferences between an array of string following the pattern
key=value or an array of @Property(name=xxx, value=xxxx))
wdyt?
> Introduce @MBean.type() to customize type in JMX bean objectName
> ----------------------------------------------------------------
>
> Key: DELTASPIKE-1008
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1008
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.5.0
> Reporter: Falko Modler
> Assignee: Romain Manni-Bucau
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: MBean_type_configurable.patch
>
>
> The {{type}} part in a JMX bean's {{objectName}} is the only thing that is
> not yet configurable. The attached patch changes that by introducing
> {{@MBean.type()}} similar to {{@MBean.category()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
