[
https://issues.apache.org/jira/browse/FELIX-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477657#comment-13477657
]
Georg Henzler edited comment on FELIX-3711 at 10/17/12 6:25 AM:
----------------------------------------------------------------
I think Confluence is a slightly broader use case, as the users enter links
themselves in a rich text editor. But maybe we should think about URL design in
general before we proceed... let's compare the following:
http://localhost:4000/system/console/bundles/24
http://localhost:4000/system/console/bundles/org.apache.felix.webconsole:3.1.9.R1239093
Shouldn't we get rid of the number-id link altogether? What's the benefit of
having them? Let's compare:
PRO: Id-Link:
- it's shorter
- makes bundle id quickly prominently available (but this info is rarely needed
by an admin)
PRO: Rest-Link:
- Shows the real technical id of a bundle in the link
- Makes the Link bookmarkable across software deployments (bundle ids might
change)
- Link can be used in Emails/Skype/Jira etc.
- Switch between DEV/INT/PROD environments can be done by just replacing the
domain (we have bookmarklets to do this!)
- and eventually: My patch from above makes the REST link available for users
that know they can click the symbolic name of the bundle, but making the REST
links default would mean that everyone would automatically benefit from them!
What do you think? (I'm aware I might totally miss something as I don't know
the web console as well as you do!)
was (Author: henzlerg):
I think Confluence is a slightly broader use case, as the users enter links
themselves in a rich text editor. But maybe we should think about URL design in
general before we proceed... let's compare the following:
http://localhost:4000/system/console/bundles/24
http://localhost:4000/system/console/bundles/org.apache.felix.webconsole:3.1.9.R1239093
Shouldn't we get rid of the number-id link altogether? What's the benefit of
having them? Let's compare:
PRO: Id-Link:
- it's shorter
- makes bundle id quickly prominently available (but this info is rarely needed
by an admin)
PRO: Rest-Link:
- Shows the real technical id of a bundle in the link
- Makes the Link bookmarkable across software deployments (bundle ids might
change)
- Link can be used in Emails/Skype/Jira etc.
- Switch between DEV/INT/PROD environments can be done by just replacing the
domain (we have bookmarklets to do this!)
- and eventually: My patch from above makes the REST link available for users
that know they can click the symbolic name of the bundle, but making the REST
links default would mean that everyone would automatically benefit from them!
What do you think? (I'm aware I might totally miss something as I don't know
the web console as well as you do!)
> Make more REST Urls available in UI (component id/name and service pid is
> often not clickable)
> ----------------------------------------------------------------------------------------------
>
> Key: FELIX-3711
> URL: https://issues.apache.org/jira/browse/FELIX-3711
> Project: Felix
> Issue Type: New Feature
> Components: Web Console
> Affects Versions: webconsole-4.0.0
> Reporter: Georg Henzler
> Attachments: org.apache.felix.webconsole.patch-for-FELIX-3711-v2.patch
>
>
> Many REST urls already work if created manually, but are not yet available as
> links in the UI:
> http://localhost:8080/system/console/bundles/org.apache.felix.webconsole
> http://localhost:8080/system/console/bundles/org.apache.felix.webconsole:4.0.1.SNAPSHOT
> http://localhost:8080/system/console/configMgr/org.apache.felix.webconsole.plugins.event.internal.PluginServlet
> http://localhost:8080/system/console/components/com.test.scr.ClassB
> It would be easy to put the appropriate link behind the property values in
> bundles/configuration/services detail views.
> I use the REST Urls a lot as they are really valuable in email/instant
> messenger/JIRA/WIKI to bring people with one click to the desired location,
> therefore it would be nice to not have to construct them manually.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
