[
https://issues.apache.org/jira/browse/RAVE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098787#comment-13098787
]
Olexiy Chudnovskyy commented on RAVE-249:
-----------------------------------------
i think it is reasonable, especially if the widget repository should be under
external administrative control. This way it can be maintained and populated by
other people and tools, provide different interfaces and various functionality
set.A very good idea would be also to standardize the remote widget repository
API, e.g. by describing its interface (REST/SOAP/...)
> As a system manager I can choose to connect Rave to either the local, default
> Widget Repository or an external Widget Repository via an API
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RAVE-249
> URL: https://issues.apache.org/jira/browse/RAVE-249
> Project: Rave
> Issue Type: Story
> Reporter: Scott Wilson
>
> I want the option to use an external service for a Widget Repository for the
> purpose of discovering widgets (see e.g. RAVE-67) instead of the default
> local repository. For example, using a REST API to query a SOLR index or
> execute SPARQL queries on a remote triplestore.
> (This could be implemented using a "remote" implementation of the
> WidgetRepository interface that can be switched via user configuration.)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
