[ 
https://issues.apache.org/jira/browse/ISIS-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438752#comment-15438752
 ] 

Dan Haywood commented on ISIS-1180:
-----------------------------------

Steve subsequently commented (in http://markmail.org/message/ps5qsvnpr3cxa636):

reading [this ticket] now its not that clear my meaning, but (maybe to make it 
even
less clear) I had the idea of 'property view models'. These could be
assigned to a property via another naming convention, maybe facadeXxx()?

e.g.

public ObjectThatOnlyHasAName getNameObject(){
return this.o;
}

public void setNameObject(ObjectThatOnlyHasAName o){
this.o = o;
}

public String facadeNameObject(
return this.o.getName();
)

another example could be to represent a String property as a hyperlink.

public String getMyUrlString()

public void setMyUrlString(String url)

public URL facadeMyUrlString()


> 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.17.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. 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, often provided as XML, building a 
> message requires navigating the hierarchy to find a specific item (leaf 
> node). This suggestion is aimed to provide a means of injesting such XML into 
> Apache Isis, maybe after some simple XSLT transformation.
> 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)

Reply via email to