[
https://issues.apache.org/jira/browse/ISIS-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Cameron updated ISIS-1180:
--------------------------------
Description:
Essentially this is a suggestion to emulate the <select> tag in HTML, where you
define as child elements <option> tags, these will have a value and a name, the
value is the key, the name is what the user sees in the select list.
In Isis its sensible to manage these binary objects in the same way as all
other persistent entities are, but to display the selected value simply as text
and not as a link.
By defining these types using another DomainObject category they can be used
via an injected domain service (maybe:
@DomainService(nature=NatureOfService.REFERENCE).
A possible further enhancement is to have the capacity for nesting of these
types be nested. This would then provide for classification hierarchies to be
defined and used. When sending messages to external systems often such systems
define catalogues in a hierarchical manner.
Such data is usually very static and of small quantity, so it can be loaded
once into a singleton and kept in global memory.
was:It makes sense to define code-list entries as objects so that they can be
managed in the same way as other kinds of objects in Isis. However, such
objects (e.g Color, Region, Salutation) are likely to have only one property,
the code 'value' or 'name'. If another type of complex object has a property of
type Color say, it makes no sense to display the assigned Color as an object
(with an icon and a link), as there is no reason to navigate to that code-list
entry object, all we want to see is the title(), which will be the value.
> Make it possible to declare some object type properties display as values only
> ------------------------------------------------------------------------------
>
> Key: ISIS-1180
> URL: https://issues.apache.org/jira/browse/ISIS-1180
> Project: Isis
> Issue Type: Improvement
> Components: Core: Viewer: Wicket
> Affects Versions: 1.9.0
> Reporter: Steve Cameron
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: 1.13.0
>
>
> Essentially this is a suggestion to emulate the <select> tag in HTML, where
> you define as child elements <option> tags, these will have a value and a
> name, the value is the key, the name is what the user sees in the select
> list.
> In Isis its sensible to manage these binary objects in the same way as all
> other persistent entities are, but to display the selected value simply as
> text and not as a link.
> By defining these types using another DomainObject category they can be used
> via an injected domain service (maybe:
> @DomainService(nature=NatureOfService.REFERENCE).
> A possible further enhancement is to have the capacity for nesting of these
> types be nested. This would then provide for classification hierarchies to be
> defined and used. When sending messages to external systems often such
> systems define catalogues in a hierarchical manner.
> Such data is usually very static and of small quantity, so it can be loaded
> once into a singleton and kept in global memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
