rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Sharples (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RAVE-789) Autodeploy W3C widgets into Rave as they are imported in Wookie
Date Tue, 04 Sep 2012 13:19:07 GMT

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

Paul Sharples updated RAVE-789:
-------------------------------

    Attachment: rave-widget-autodeploy.patch

I have attached a patch with what I had in mind.  I'd like if possible for someone else to
take a quick look at it rather than just commit it as is.  Thanks.
                
> Autodeploy W3C widgets into Rave as they are imported in Wookie
> ---------------------------------------------------------------
>
>                 Key: RAVE-789
>                 URL: https://issues.apache.org/jira/browse/RAVE-789
>             Project: Rave
>          Issue Type: New Feature
>          Components: rave-web
>    Affects Versions: 0.15
>         Environment: N/A
>            Reporter: Paul Sharples
>            Assignee: Paul Sharples
>            Priority: Minor
>         Attachments: rave-widget-autodeploy.patch
>
>
> I have a requirement from the omelette project. When a widget is imported into wookie,
the same widget would also be made available in Rave without the need for further administration/approval.
> The idea is...
> 1 A user imports a new W3C widget into Wookie.
> 2 Wookie then fires a POST event to a new service in Rave (sending the identifier of
the new widget along with it)
> 3 If this service/feature is enabled in portal.properties (do 4 & 5), otherwise reject
the request
> 4 Rave uses the new service to first get the metadata and do the usual checks on the
widget (queries Wookie using the widget identifier)
> 5 Rave imports the W3C widget from Wookie and makes it available
> To be able to add a new widget to Rave, there must be a User object available with [ROLE_USER]
permissions. Because this is a request from another application, I propose to create a "System"
user account on the fly, which would be then revoked once the request has completed.  This
feature would be disabled by default in portal.properties. The "System" user id would also
be defined in portal.properties.
> Also see WOOKIE-362.

--
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

Mime
View raw message