[
https://issues.apache.org/jira/browse/FELIX-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856043#action_12856043
]
Justin Edelson commented on FELIX-2274:
---------------------------------------
> Well, actually at this point the plugin is not available anymore, so it can't
> redirect.
Hmmm. You said "a plugin developer might decide to show the plugin..." so why
couldn't the plugin developer choose to show a different servlet? But if you're
talking about a plugin registered via SCR or Blueprint, this would be more
challenging (although not impossible).
>And it's not confusing, because at the top, the bundles tab will be rendered
>as "selected".
Which will result in "But I asked for the [fill in the blank] plugin!" And
they're going to click on the [fill in the blank] button again... and again...
and again...
All I'm suggesting is that you have to have some message to the user.
> 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
