You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2012/12/17 10:26:13 UTC

[jira] [Closed] (ISIS-194) Allow JSON viewer to work with object stores other than the in-memory objectstore.

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

Dan Haywood closed ISIS-194.
----------------------------


prior to generating 1.0.0 release notes
                
> Allow JSON viewer to work with object stores other than the in-memory objectstore.
> ----------------------------------------------------------------------------------
>
>                 Key: ISIS-194
>                 URL: https://issues.apache.org/jira/browse/ISIS-194
>             Project: Isis
>          Issue Type: Improvement
>          Components: Core, Objectstore: SQL, Viewer: RestfulObjects
>    Affects Versions: 0.2.0-incubating
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>             Fix For: isis-viewer-restfulobjects-1.0.0
>
>
> In attempting to get the json viewer to run with the SQL object store, discovered that it makes the wrong call to the AdapterManager and so fails to load objects via its OID.
> Exploring further, realized that the SqlOid impl *does* include the relevant information to call the right API of AdapterManager / PersistenceSession, namely that the className (=> objectSpec) is also included.
> This change is therefore to introduce a new subtype of Oid, namely OidWithSpecification, that is a self-contained Oid, and have the json viewer depend only on object stores that support OidWithSpecification.  (Note: it isn't practicable to do what the html and scimpi viewers do, which is to cache the spec per Oid in session state, since the idea is that the json viewer is entirely stateless).
> Also retrofit SqlOid to implement this new interface.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira