[
https://issues.apache.org/jira/browse/KARAF-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592011#comment-14592011
]
Jean-Baptiste Onofré edited comment on KARAF-3793 at 6/19/15 4:40 AM:
----------------------------------------------------------------------
To reproduce the problem:
{code}
karaf@root()> feature:install webconsole
{code}
First, we can see a refresh of the shell console (whereas it didn't happen with
Karaf 4.0.0.M3).
Secondly, the webconsole feature installation works fine, but the jetty
connector is not bound meaning that at least the webconsole servlet is not
registered (that we can see with http:list command).
(As reminder, feature:install webconsole works fine with Karaf 4.0.0.M3).
Here's what I tested:
- Felix Framework 5.0.1 and Resolver 1.4.0 (staging) with latest Pax Web
4.1.3-SNAPSHOT, ignoreServiceReq=true (default): installation is OK, shell
console is refreshed, jetty connector is not bound, and lot of bundles are
missing (jetty bundles)
- Felix Framework 5.0.1 and Resolver 1.4.0 (staging) with latest Pax Web
4.1.3-SNAPSHOT, ignoreServiceReq=false: installation is OK, shell console is
refreshed, jetty connector is not bound, and lot of bundles are missing (jetty
bundles)
- Felix Framework 5.0.1 and Resolver 1.4.0 (staging) with Pax Web 4.1.2,
ignoreServiceReq=true (default): installation is OK, shell console is
refreshed, jetty bundles are now installed but not started. Starting the
bundles (with bundle:start 1-92) starts the webconsole.
- Felix Framework 5.0.0 and Resolver 1.2.0 (downgrade) with Pax Web
4.1.3-SNAPSHOT: installation is OK, shell console is refreshed, jetty connector
is not bound, and lot of bundles are missing (jetty bundles)
- Felix Framework 5.0.0 and Resolver 1.2.0 (downgrade) with Pax Web 4.1.2:
I gonna try to add pax-jetty feature in dependency of webconsole: it should
help at least for the jetty bundles.
So, it looks like a combination of change in Pax Web (for the jetty bundles)
and the resolver (as they stay in installed state).
was (Author: jbonofre):
To reproduce the problem:
{code}
karaf@root()> feature:install webconsole
{code}
First, we can see a refresh of the shell console (whereas it didn't happen with
Karaf 4.0.0.M3).
Secondly, the webconsole feature installation works fine, but the jetty
connector is not bound meaning that at least the webconsole servlet is not
registered (that we can see with http:list command).
(As reminder, feature:install webconsole works fine with Karaf 4.0.0.M3).
Here's what I tested:
- Felix Framework 5.0.1 and Resolver 1.4.0 (staging) with latest Pax Web
4.1.3-SNAPSHOT, ignoreServiceReq=true (default): installation is OK, shell
console is refreshed, jetty connector is not bound, and lot of bundles are
missing (jetty bundles)
- Felix Framework 5.0.1 and Resolver 1.4.0 (staging) with latest Pax Web
4.1.3-SNAPSHOT, ignoreServiceReq=false: installation is OK, shell console is
refreshed, jetty connector is not bound, and lot of bundles are missing (jetty
bundles)
- Felix Framework 5.0.1 and Resolver 1.4.0 (staging) with Pax Web 4.1.2,
ignoreServiceReq=true (default): installation is OK, shell console is
refreshed, jetty bundles are now installed but not started. Starting the
bundles (with bundle:start 1-92) starts the webconsole.
- Felix Framework 5.0.0 and Resolver 1.2.0 (downgrade) with Pax Web
4.1.3-SNAPSHOT:
- Felix Framework 5.0.0 and Resolver 1.2.0 (downgrade) with Pax Web 4.1.2:
I gonna try to add pax-jetty feature in dependency of webconsole: it should
help at least for the jetty bundles.
So, it looks like a combination of change in Pax Web (for the jetty bundles)
and the resolver (as they stay in installed state).
> WebConsole installs but it's not actually available
> ---------------------------------------------------
>
> Key: KARAF-3793
> URL: https://issues.apache.org/jira/browse/KARAF-3793
> Project: Karaf
> Issue Type: Bug
> Components: karaf-webconsole
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Blocker
> Fix For: 4.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
