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

ASF subversion and git services commented on ISIS-933:
------------------------------------------------------

Commit 97abf1b441e813a18a637d64d07ae31c1c934fd3 in isis's branch 
refs/heads/ISIS-993 from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=97abf1b ]

ISIS-933: fixing layout issues when the layout.xml HAS been specified...

* was adding in properties to fieldsets twice, even if already in the fieldset. 
 (This bug because previously I had been focusing on getting the auto-add for 
non-referenced properties to work, based on @MemberOrder)

Also:
* ensuring that can reload dynamically without having to invalidate cache.  
This bug was due to the SpeificationCacheDefault ( which maintains two separate 
hashmaps to cache specs) getting out-of-whack internally ... specId holding one 
version of a spec, while className holding a different on.
* remove versionSequence from SimpleObject (as now have the Persistable_... 
mixins).


> Allow the RO viewer to be configured so that it can honour or ignore UI hints 
> (in particular, the @Render(EAGERLY) facet).
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-933
>                 URL: https://issues.apache.org/jira/browse/ISIS-933
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core: Viewer: RestfulObjects
>    Affects Versions: core-1.7.0
>            Reporter: Dan Haywood
>            Priority: Minor
>             Fix For: core-1.8.0
>
>
> Currently in Estatio, retrieving a Property entity results in a 2.6Mb 
> response.  This is  because its 'Units' collection is annotated as an eagerly 
> rendered.
> We expect that most RO clients to be "data" API clients, ie will make their 
> own decisions about which data to retrieve and how. 
> For this ticket, suggest simply a global configuration setting:
> # whether to honor UI hints, in particular Render(EAGERLY).  Default to false.
> #isis.viewer.restfulobjects.honorUiHints=false
> ~~~
> In the future, this could be generalized/refined by having the RO client send 
> an HTTP Accept header and have the RO viewer server respond appropriately.



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

Reply via email to