From: Robert Weeks <RWeeks_at_ext-inc.com>
Date: Fri, 2 Sep 2011 09:21:14 -0700

Thanks Sahoo -

Putting a dummy activator in an early library that is required to do the below seems to have worked. Thanks for the suggestion.


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

________________________________________
From: Sahoo [sanjeeb.sahoo_at_oracle.com]
Sent: Tuesday, August 30, 2011 11:54 PM
To: Robert Weeks
Cc: users_at_glassfish.java.net
Subject: Re: GlassFish 3.1.1 - OSGi HTTP Service Implementation not starting

Robert,

Yes, somehow you have to load a class from osgi-http bundle. You can
just have a dummy ServiceTracker tracking HttpService in your bundle
activator. That's what I do in our http sample as you can see here:
https://svn.java.net/svn/glassfish~svn/trunk/fighterfish/sample/osgihttp/helloworld/src/main/java/org/glassfish/fighterfish/sample/osgihttp/helloworld/HelloWorldHttpActivator.java

Hope that's acceptable to you. If you really don't want to do this, then
you can actually configure GlassFish to start all lazy bundles eagerly
by setting glassfish.osgi.auto.start.options=0 in
felix/conf/config.properties.

Thanks,
Sahoo