[
https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190964#comment-13190964
]
Scott Wilson commented on RAVE-256:
-----------------------------------
Hi Jose
Spring can automatically generate JSON in response to a request for the JSON
type in the Accepts header, so there isn't really any extra overhead in also
offering JSON export.
The XML is a different proposition as there we'd want to have a standard
information model that was stable across versions rather than just output the
current model.
(Ideally, we'd like to have a standard page export model that we could also use
with other products as well as Rave, e.g. SAP StreamWork, LifeRay)
S
> As a user I want to export a page model so that I can use it elsewhere
> ----------------------------------------------------------------------
>
> Key: RAVE-256
> URL: https://issues.apache.org/jira/browse/RAVE-256
> Project: Rave
> Issue Type: Story
> Reporter: Scott Wilson
> Assignee: Scott Wilson
> Fix For: 0.4-INCUBATING
>
>
> This is the capability to export a page model using a representation such as
> XML or JSON, for example for importing into another Rave server, or to submit
> it to a "workspace registry" (see RAVE-26). The exported page would include
> the region, layout and widgets, but not any user data or preferences, so it
> would function more as a template than an archive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
