You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ian Main (JIRA)" <qp...@incubator.apache.org> on 2010/01/06 21:43:54 UTC

[jira] Commented: (QPID-1880) The new unmanaged objects are confusing

    [ https://issues.apache.org/jira/browse/QPID-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797303#action_12797303 ] 

Ian Main commented on QPID-1880:
--------------------------------

Actually we had a conversation on irc and figured that so long as all the properties of a class were read only, then the 'unmanaged' part happens automatically.  Therefore it should be enforced that unmanaged objects contain only read only attributes.

> The new unmanaged objects are confusing
> ---------------------------------------
>
>                 Key: QPID-1880
>                 URL: https://issues.apache.org/jira/browse/QPID-1880
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Qpid Managment Framework
>            Reporter: Ian Main
>
> IMO the newly added managed objects are confusing in that they return and look just like the managed objects, but you are unable to call methods on them, nor use eg the refresh() method to get a newly updated instance.
> QMF up until this point has made all objects managed and backed by an implementation.  The addition of a data structure type could be very useful but I don't think it should share the same name as the managed objects around which QMF revolves.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org