[
https://issues.apache.org/jira/browse/FELIX-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856128#action_12856128
]
Justin Edelson commented on FELIX-2274:
---------------------------------------
> Another possibility, is that Web Console generates a page, that says "plugin
> A is no longer available, you will be redirected to the default plugin in few
> seconds", and after that period the user will get to the default plugin,
> without need to click anything.
This is a good solution.
> 404 when plugin is missing
> --------------------------
>
> Key: FELIX-2274
> URL: https://issues.apache.org/jira/browse/FELIX-2274
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Reporter: Valentin Valchev
>
> Currently the Web Console generates 404 (page not found) error, when a plugin
> is missing.
> But a plugin developer might devicide to show the plugin, only when all
> required services are available. If the user already opened the web console,
> the label for such plugin will be rendered. After that, a required service is
> unregistered and so is the plugin.
> At this point, when the user clicks on the label, the Web Console will
> generate 404.
> IMHO, it's will be better, if the web console simply redirects to the default
> plugin (bundles).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
