You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by "Scott Wilson (JIRA)" <ji...@apache.org> on 2011/09/07 18:37:09 UTC
[jira] [Created] (RAVE-256) As a user I want to export a page model
in XML so that I can use it elsewhere
As a user I want to export a page model in XML 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
This is the capability to export a page model using an XML representation, 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (RAVE-256) As a user I want to export a page model so that I can use it elsewhere
Posted by Scott Wilson <sc...@gmail.com>.
On 27 Jan 2012, at 08:05, Jose Badeau wrote:
> Hey Scott I'm not exactly sure how I should involve myself. I have a design
> in mind for a way to make the front-end pluggable like the java side.
> Should I submit a design spec or talk to someone?
You can discuss the idea here on the list, or if you want you can put together a proposal doc and add that to an issue in Jira depending on what works best for you. I think most people here are quite open to ideas when it comes to how the UI is managed longer term (v2.0?), so kicking off that discussion would be good. Though I think for now the emphasis is on having a reasonably feature-complete application.
> I really think jsps are
> not the way but rather json to HTML conversion using something like pure
> js. The idea is to provide a data model apply HTML templates, generate HTML
> and them apply styles.
OK, so is basically the idea to work primarily on the API, and then the front end UI is just another client?
I like the toolkit idea for making theming easier - I guess something similar to Twitter Bootstrap?
> The styles should be designed like a toolkit (dojo,
> extjs) widgets .menu .ui-button rather than #nav .nav-item. This way
> clients can easily theme the portal, change the markup, and upgrade easily.
> I am away on vacation for 1.5 weeks then ready to contribute. I will write
> up the design and submit it then. I dont won't to be counter productive
> with other peoples work do if there is someone I should contact just let me
> know.
Great! As for how it affects other work, thats for the community to feed back on - as I said above I can't see Rave accepting a major change to how the UI is managed immediately, but we do need the UI to be easily themed and customised, and longer term I think the options are still open for how we can best do that.
My personal interest is in the API for export and import of pages between different instances of Rave or between Rave and other platforms such as iGoogle (e.g. GadgetTabML) and LifeRay. The project I work on (OMELETTE) has starting working on a spec for this use case, we're just discussing now how we might take that forward in a more open way. But I think thats a different semi-related discussion.
>
> Cheers from switzerland
> Jose
>
> On Monday, January 23, 2012, Scott Wilson (Commented) (JIRA) <
> jira@apache.org> wrote:
>>
>> [ https://issues.apache.org/jira/browse/RAVE-256?n to hrml
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191220#comment-13191220
> ]
>>
>> Scott Wilson commented on RAVE-256:
>> -----------------------------------
>>
>> Yes you're correct - currently the page export model uses JAXB
> annotations on some parts of the model rather than the whole model. I saw
> the model on RAVE-26 comments and we should definitely work together on
> this one.
>>
>>> 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
>>
>>
>>
[jira] [Commented] (RAVE-256) As a user I want to export a page model
so that I can use it elsewhere
Posted by Jose Badeau <jo...@gmail.com>.
Hey Scott I'm not exactly sure how I should involve myself. I have a design
in mind for a way to make the front-end pluggable like the java side.
Should I submit a design spec or talk to someone? I really think jsps are
not the way but rather json to HTML conversion using something like pure
js. The idea is to provide a data model apply HTML templates, generate HTML
and them apply styles. The styles should be designed like a toolkit (dojo,
extjs) widgets .menu .ui-button rather than #nav .nav-item. This way
clients can easily theme the portal, change the markup, and upgrade easily.
I am away on vacation for 1.5 weeks then ready to contribute. I will write
up the design and submit it then. I dont won't to be counter productive
with other peoples work do if there is someone I should contact just let me
know.
Cheers from switzerland
Jose
On Monday, January 23, 2012, Scott Wilson (Commented) (JIRA) <
jira@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/RAVE-256?n to hrml
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191220#comment-13191220
]
>
> Scott Wilson commented on RAVE-256:
> -----------------------------------
>
> Yes you're correct - currently the page export model uses JAXB
annotations on some parts of the model rather than the whole model. I saw
the model on RAVE-26 comments and we should definitely work together on
this one.
>
>> 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
>
>
>
[jira] [Commented] (RAVE-256) As a user I want to export a page
model so that I can use it elsewhere
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106772#comment-13106772 ]
Scott Wilson commented on RAVE-256:
-----------------------------------
No worries Matt I did spot the commit :-)
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (RAVE-256) As a user I want to export a page
model in XML so that I can use it elsewhere
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099083#comment-13099083 ]
Scott Wilson commented on RAVE-256:
-----------------------------------
Agreed - I think a REST API supporting both JSON and XML serialization would be good for interoperability with external tools.
> As a user I want to export a page model in XML 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
>
> This is the capability to export a page model using an XML representation, 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (RAVE-256) As a user I want to export a page
model so that I can use it elsewhere
Posted by "Scott Wilson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191220#comment-13191220 ]
Scott Wilson commented on RAVE-256:
-----------------------------------
Yes you're correct - currently the page export model uses JAXB annotations on some parts of the model rather than the whole model. I saw the model on RAVE-26 comments and we should definitely work together on this one.
> 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
[jira] [Resolved] (RAVE-256) As a user I want to export a page
model so that I can use it elsewhere
Posted by "Matt Franklin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Franklin resolved RAVE-256.
--------------------------------
Resolution: Fixed
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (RAVE-256) As a user I want to export a page
model so that I can use it elsewhere
Posted by "Jose (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190958#comment-13190958 ]
Jose commented on RAVE-256:
---------------------------
Both websphere portal and liferay use xml to export the portal topology (navigation mode, content model, permissions) but not the users data. In fact they use separate databases for the portal and for users/personalization, etc. I dont see a big reason to export in JSON? If you need JSON on the client-side then just expose the navigation model/content model via rest services.
> 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
[jira] [Commented] (RAVE-256) As a user I want to export a page
model in XML so that I can use it elsewhere
Posted by "Marlon Pierce (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099081#comment-13099081 ]
Marlon Pierce commented on RAVE-256:
------------------------------------
JSON serialization would also be nice.
> As a user I want to export a page model in XML 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
>
> This is the capability to export a page model using an XML representation, 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (RAVE-256) As a user I want to export a page
model so that I can use it elsewhere
Posted by "Matt Franklin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106659#comment-13106659 ]
Matt Franklin commented on RAVE-256:
------------------------------------
Oops... I missed your comment (and ticket assignment). If you update, you will see the new method there.
http://server.domain/portal/app/api/rest/page/pageId will output either XML or JSON (depending on your accept header)
http://server.domain/portal/app/api/rest/page/pageId?export=true will output a simplified version with no preferences or owner information
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (RAVE-256) As a user I want to export a page model
so that I can use it elsewhere
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Wilson updated RAVE-256:
------------------------------
Description: 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. (was: This is the capability to export a page model using an XML representation, 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.)
Summary: As a user I want to export a page model so that I can use it elsewhere (was: As a user I want to export a page model in XML so that I can use it elsewhere)
Edited to be agnostic about serialization type (XML, JSON etc)
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (RAVE-256) As a user I want to export a page
model so that I can use it elsewhere
Posted by "Matt Franklin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104640#comment-13104640 ]
Matt Franklin commented on RAVE-256:
------------------------------------
Rave already has a content negotiating view resolver that can serialize to XML or JSON. A simple first run implementation of this could simply add a getPage method to the PageApi in o.a.r.p.web.api.rest
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (RAVE-256) As a user I want to export a page model
so that I can use it elsewhere
Posted by "Matt Franklin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Franklin updated RAVE-256:
-------------------------------
Fix Version/s: 0.4-INCUBATING
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (RAVE-256) As a user I want to export a page
model so that I can use it elsewhere
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105191#comment-13105191 ]
Scott Wilson commented on RAVE-256:
-----------------------------------
Thanks Matt - I'll add a getPage method to PageAPI and take it from there
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (RAVE-256) As a user I want to export a page
model so that I can use it elsewhere
Posted by "Jose (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190991#comment-13190991 ]
Jose commented on RAVE-256:
---------------------------
Well I assume the page export model (cross product model) would be a subset or extracted from the Rave topology model because I'm sure not all rave features would be required or usable in other containers/portals. The page export model could be exported using the rave Topology model. I have also submitted a comment to issue RAVE-26 about navigation/content model. please let me know if you would like help.
> 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
[jira] [Commented] (RAVE-256) As a user I want to export a page
model so that I can use it elsewhere
Posted by "Scott Wilson (Commented) (JIRA)" <ji...@apache.org>.
[ 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