[ 
https://issues.apache.org/jira/browse/QPID-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-7157:
-----------------------------
    Description: metadata information should drive implementation of UI widgets 
for rendering attribute values.We need to change metadata of attributes having  
enum types to list enum values in validValues property. That would allow 
creation of widgets which can represent enum attribute editor as a "select" 
widget with options containing all possible enum values   (was: metadata 
information should drive implementation of UI widgets for rendering attribute 
values. It would be nice to provide in metadata the details of such custom 
types like enums. That would allow creation of widgets which can represent enum 
attribute editor as a "select" widget with options containing all possible enum 
values )

> [Java Broker] Change metadata for management attributes having enum types to 
> list all possible enum values in validValues property
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-7157
>                 URL: https://issues.apache.org/jira/browse/QPID-7157
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: qpid-java-6.0.1
>            Reporter: Alex Rudyy
>             Fix For: qpid-java-6.1
>
>
> metadata information should drive implementation of UI widgets for rendering 
> attribute values.We need to change metadata of attributes having  enum types 
> to list enum values in validValues property. That would allow creation of 
> widgets which can represent enum attribute editor as a "select" widget with 
> options containing all possible enum values 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to