[jira] Commented: (KARAF-211) osgi:list to other command to display context-path for web applications or a new war command for that
[ https://issues.apache.org/jira/browse/KARAF-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12974349#action_12974349 ] Achim Nierbeck commented on KARAF-211: -- How about adding another column like with spring and blueprint which is optional and only available if pax-web is installed. Something like a WebContextListener similar to BlueprintListener or SpringStateListenerFactory. osgi:list could look like: ID State Blueprint Web-ContextPath Level Name [181] [Active ] [ ] [fooapp ] [ 60] fooapp (1.0.1) What do you think? osgi:list to other command to display context-path for web applications or a new war command for that - Key: KARAF-211 URL: https://issues.apache.org/jira/browse/KARAF-211 Project: Karaf Issue Type: New Feature Affects Versions: 2.0.0 Reporter: Claus Ibsen Priority: Minor When installing war files you dont know the context-path its being given. Also you may be in doubt what the http url is to access it. So if the shell console had a war command or other means to access this would be nice bundle id: 181 type: web application context-path: /fooapp full-path: http://localhost:8181/fooapp If you got many web applications it might be nice will a list of all those in one row per app, kinda like a table listed the information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-211) osgi:list to other command to display context-path for web applications or a new war command for that
[ https://issues.apache.org/jira/browse/KARAF-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12974355#action_12974355 ] Guillaume Nodet commented on KARAF-211: --- Or, as the number of webapps might not be that important compared to the number of bundles (imho), maybe as we display fragments/host instead, so displaying the webapp context on the following line ? osgi:list to other command to display context-path for web applications or a new war command for that - Key: KARAF-211 URL: https://issues.apache.org/jira/browse/KARAF-211 Project: Karaf Issue Type: New Feature Affects Versions: 2.0.0 Reporter: Claus Ibsen Priority: Minor When installing war files you dont know the context-path its being given. Also you may be in doubt what the http url is to access it. So if the shell console had a war command or other means to access this would be nice bundle id: 181 type: web application context-path: /fooapp full-path: http://localhost:8181/fooapp If you got many web applications it might be nice will a list of all those in one row per app, kinda like a table listed the information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-211) osgi:list to other command to display context-path for web applications or a new war command for that
[ https://issues.apache.org/jira/browse/KARAF-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12974362#action_12974362 ] Achim Nierbeck commented on KARAF-211: -- I just think it is helpful seeing the web-contextpath attached to the war-bundle. You are right though that a complete column could be a bit oversized :) I kind of like the fragments/host way. osgi:list to other command to display context-path for web applications or a new war command for that - Key: KARAF-211 URL: https://issues.apache.org/jira/browse/KARAF-211 Project: Karaf Issue Type: New Feature Affects Versions: 2.0.0 Reporter: Claus Ibsen Priority: Minor When installing war files you dont know the context-path its being given. Also you may be in doubt what the http url is to access it. So if the shell console had a war command or other means to access this would be nice bundle id: 181 type: web application context-path: /fooapp full-path: http://localhost:8181/fooapp If you got many web applications it might be nice will a list of all those in one row per app, kinda like a table listed the information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-211) osgi:list to other command to display context-path for web applications or a new war command for that
[ https://issues.apache.org/jira/browse/KARAF-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12974382#action_12974382 ] Andreas Pieber commented on KARAF-211: -- +1 to the fragments/host way. osgi:list to other command to display context-path for web applications or a new war command for that - Key: KARAF-211 URL: https://issues.apache.org/jira/browse/KARAF-211 Project: Karaf Issue Type: New Feature Affects Versions: 2.0.0 Reporter: Claus Ibsen Priority: Minor When installing war files you dont know the context-path its being given. Also you may be in doubt what the http url is to access it. So if the shell console had a war command or other means to access this would be nice bundle id: 181 type: web application context-path: /fooapp full-path: http://localhost:8181/fooapp If you got many web applications it might be nice will a list of all those in one row per app, kinda like a table listed the information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-211) osgi:list to other command to display context-path for web applications or a new war command for that
[ https://issues.apache.org/jira/browse/KARAF-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12935829#action_12935829 ] Guillaume Nodet commented on KARAF-211: --- I think the osgi:headers would display it when the header already exist, but maybe a web app related set of commands would be usefull. Not sure if there's a need for other commands though... Thoughts ? osgi:list to other command to display context-path for web applications or a new war command for that - Key: KARAF-211 URL: https://issues.apache.org/jira/browse/KARAF-211 Project: Karaf Issue Type: New Feature Affects Versions: 2.0.0 Reporter: Claus Ibsen Priority: Minor When installing war files you dont know the context-path its being given. Also you may be in doubt what the http url is to access it. So if the shell console had a war command or other means to access this would be nice bundle id: 181 type: web application context-path: /fooapp full-path: http://localhost:8181/fooapp If you got many web applications it might be nice will a list of all those in one row per app, kinda like a table listed the information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (KARAF-211) osgi:list to other command to display context-path for web applications or a new war command for that
[ https://issues.apache.org/jira/browse/KARAF-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12910127#action_12910127 ] Claus Ibsen commented on KARAF-211: --- When using the ?Webapp-Context option when installing the war then osgi:headers list the context path. Otherwise not. osgi:list to other command to display context-path for web applications or a new war command for that - Key: KARAF-211 URL: https://issues.apache.org/jira/browse/KARAF-211 Project: Karaf Issue Type: New Feature Affects Versions: 2.0.0 Reporter: Claus Ibsen Priority: Minor When installing war files you dont know the context-path its being given. Also you may be in doubt what the http url is to access it. So if the shell console had a war command or other means to access this would be nice bundle id: 181 type: web application context-path: /fooapp full-path: http://localhost:8181/fooapp If you got many web applications it might be nice will a list of all those in one row per app, kinda like a table listed the information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
