felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-566) More RESTful management console URLs
Date Thu, 19 Jun 2008 11:09:45 GMT

    [ https://issues.apache.org/jira/browse/FELIX-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606329#action_12606329
] 

Felix Meschberger commented on FELIX-566:
-----------------------------------------

Enabled RESTful URLs for component list in Rev. 669450.

Together with this enhancement the display of the bundles and components has been unified

> More RESTful management console URLs
> ------------------------------------
>
>                 Key: FELIX-566
>                 URL: https://issues.apache.org/jira/browse/FELIX-566
>             Project: Felix
>          Issue Type: Improvement
>          Components: Web Console
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> Currently the Management Console URLs are not really REST-ful:
> > To get a list of bundles you access /system/console/list. This should rather be
/system/console/bundles.
> > To get bundle details the URL is /system/console/bundledetails with a request property
naming the bundle whose details are to be returned. This should rather be /system/console/bundles/x
where x is the bundleID or some other identification of the bundle to access
> > To start (or stop or uninstall) a bundle a request to /system/console with an action
parameter and a bundleId parameter is POSTed to the console. This should rather use the bundle
URL - /system/console/bundles/x as above - and an action parameter denoting the action.
> > It should be possible to directly access a certain configuration by URL such as
/system/console/configurations/<pid> where <pid> is the PID of the configuration
or access /system/console/configurations to get all configurations.
> > etc.
> As a corollary to these changes the current interfaces Action and Render should be dropped
and replaced by the venerable Servlet interface. This makes implementation of the URLs easier.
On the downside, this might create big servlets for the HTML rendering, which might be solved
by using helper classes.
> The servlets will need to be registered as OSGi services with appropriate service registration
properties. The Console will only pick up servlets registered with the correct property settings.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message