Hi Robert,
No, you don't have to explicitly start it. You see it in Starting state,
because it uses "LAZY ACTIVATION" policy. This bundle exports
org.osgi.service.http package, so if you deploy your own bundle that
uses httpservice API from this bundle, then it will automatically get
activated. I felt this is better than user having to download and
deploy osgi-http.jar from somewhere.
Thanks,
Sahoo
On Wednesday 31 August 2011 12:39 AM, Robert Weeks wrote:
> Hello -
>
> On a fresh install of GF3.1.1 - when looking at the bundles (gogo -> lb) - it always says the OSGi HTTP Service Implementation for GlassFish Web Container (1.0.4) is "Starting" - and never completely starts unless I kickstart it by telling it to start in the console.
>
> We rely on this - and with GF 3.1 - we installed the bundle into the modules/autostart directory. I thought I could get rid of that step with 3.1.1 - but if we manually have to tell that bundle to start before it will complete, we won't be able to use this.
>
> Is there a reason for this?
>
> Thanks for any information.
>
>
> Robert Weeks
> Lead Developer - Framework and UI
> EXTENSION, INC.
> Email: rweeks_at_ext-inc.com
> Office: 260-797-0200 x4228
> General: 877-207-3753
> www.OpenTheRedBox.com
>
> Download the FREE EXTENSION Mobile App for iPhone and iPod Touch
> http://www.opentheredbox.com/iPhone_appDemo.php
>
> Download the FREE EXTENSION Mobile App for Android-Based Devices
> https://market.android.com/details?id=com.ext_inc.android&feature=search_result
>
> We're Exhibiting in an Area Near You
> http://www.opentheredbox.com/events.php
>