[jboss-jira] [JBoss JIRA] Updated: (JBAS-6721) a few Topic/Queue ManagedProperties have the wrong ViewUse

Ian Springer (JIRA) jira-events at lists.jboss.org
Wed Apr 1 17:54:39 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBAS-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Springer updated JBAS-6721:
-------------------------------

    Description: 
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the xml config file, e.g.:

<mbean xmbean-dd="xmdesc/Topic-xmbean.xml" name="jboss.messaging.destination:service=Topic,name=MyTopic" code="org.jboss.jms.server.destination.TopicService">

At least I think the name=MyTopic portion of the MBean name becomes the Topic's name.

Actually 'name' should probably *only* be settable at the time of creation and after that be read-only. In JON we allow the GUI user to set values on properties that are both required and read-only and that currently have null values, but at other times, those properties cannot be modified. We do this mainly for the creation use case - for example, in the case of the 'name' prop, we would make it read-only and required, so the user would be forced to specify a value at Topic/Queue creation time, but then would not be able to change it once the Topic/Queue has been created.

2) 'createdProgrammatically' sounds like it should be read-only and hence STATISTIC rather than RUNTIME

3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since it can be set in the xml config file, e.g.:

<attribute name="MessageCounterHistoryDayLimit">10</attribute> 




  was:
1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the xml config file, e.g.:

<mbean xmbean-dd="xmdesc/Topic-xmbean.xml" name="jboss.messaging.destination:service=Topic,name=MyTopic" code="org.jboss.jms.server.destination.TopicService">

At least I think the name=MyTopic portion of the MBean name becomes the Topic's name.

2) 'createdProgrammatically' sounds like it should be read-only and hence STATISTIC rather than RUNTIME

3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since it can be set in the xml config file, e.g.:

<attribute name="MessageCounterHistoryDayLimit">10</attribute> 






> a few Topic/Queue ManagedProperties have the wrong ViewUse
> ----------------------------------------------------------
>
>                 Key: JBAS-6721
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6721
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: ProfileService
>            Reporter: Ian Springer
>            Assignee: Scott M Stark
>            Priority: Critical
>
> 1) 'name' prop - should be CONFIGURATION, not RUNTIME, since it can be set in the xml config file, e.g.:
> <mbean xmbean-dd="xmdesc/Topic-xmbean.xml" name="jboss.messaging.destination:service=Topic,name=MyTopic" code="org.jboss.jms.server.destination.TopicService">
> At least I think the name=MyTopic portion of the MBean name becomes the Topic's name.
> Actually 'name' should probably *only* be settable at the time of creation and after that be read-only. In JON we allow the GUI user to set values on properties that are both required and read-only and that currently have null values, but at other times, those properties cannot be modified. We do this mainly for the creation use case - for example, in the case of the 'name' prop, we would make it read-only and required, so the user would be forced to specify a value at Topic/Queue creation time, but then would not be able to change it once the Topic/Queue has been created.
> 2) 'createdProgrammatically' sounds like it should be read-only and hence STATISTIC rather than RUNTIME
> 3) 'messageCounterHistoryDayLimit' should be CONFIGURATION, not STATISTIC, since it can be set in the xml config file, e.g.:
> <attribute name="MessageCounterHistoryDayLimit">10</attribute> 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list