[
https://issues.apache.org/jira/browse/FELIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler closed FELIX-900.
--------------------------------
Resolution: Invalid
Must have been a bug on my HttpService. Thanks for looking into this.
> WebConsole does not register servlet when HttpService already registered
> ------------------------------------------------------------------------
>
> Key: FELIX-900
> URL: https://issues.apache.org/jira/browse/FELIX-900
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-1.2.2
> Reporter: Thomas Diesler
> Assignee: Felix Meschberger
>
> Looking at
> public OsgiManager( BundleContext bundleContext )
> {
> this.bundleContext = bundleContext;
> this.log = new Logger( bundleContext );
> updateConfiguration( null );
> try
> {
> this.configurationListener = ConfigurationListener.create( this );
> }
> catch ( Throwable t )
> {
> // might be caused by CM not available
> }
> // get at the HttpService first, this should initialize
> // the OSGi Manager and start the initial setup
> httpServiceTracker = new HttpServiceTracker( this );
> httpServiceTracker.open();
> }
> it seems that the manager servlet is only registered when the HttpService
> comes *after* the webconsole service
> public Object addingService( ServiceReference reference )
> {
> Object operation = super.addingService( reference );
> if ( operation instanceof HttpService )
> {
> osgiManager.bindHttpService( ( HttpService ) operation );
> }
> return operation;
> }
> Unless I miss something, the OsgiManager should probably check for
> HttpService and register it's servlet when the OsgiManager is activated
> public void start( BundleContext bundleContext )
> {
> osgiManager = new OsgiManager( bundleContext );
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
