[
https://issues.apache.org/jira/browse/FELIX-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597921#action_12597921
]
fmeschbe edited comment on FELIX-568 at 5/19/08 4:06 AM:
------------------------------------------------------------------
Yes, the code is already in Apache Felix. But don't hurry creating another
patch.
It is very well possible, that the extension API is modified into just being
Servlets instead of Action/Renderer interfaces.
was (Author: fmeschbe):
Don't hurry creating another patch.
It is very well possible, that the extension API is modified into just being
Servlets instead of Action/Renderer interfaces.
> [Patch] Separate bundle details page in sling web console
> ---------------------------------------------------------
>
> Key: FELIX-568
> URL: https://issues.apache.org/jira/browse/FELIX-568
> Project: Felix
> Issue Type: New Feature
> Components: Web Console
> Reporter: Alexander Klimetschek
> Assignee: Felix Meschberger
> Attachments: bundle-details-html-page.patch,
> bundle-details-html-page.patch, bundle-details-html-page.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This patch adds a separate HTML page showing bundle details to the Sling web
> console. It displays the same details as those displayed by the ajax-based
> "popup".
> Use case: I found myself configuring a bundle with Export-Package etc. and
> continuously installing it to Sling to see if all package dependencies could
> be resolved. It is quite tedious to reload the bundle list page, scroll down
> to the bundle in question and click on the link to get the ajax-based details
> popup. A simpler (and more restful) way is to have a separate URL and HTML
> page for a single bundle's details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
