Well thanks a lot. I've placed it under www.furiousbob.com/spotlight.zip(Sorry we are still working on a public svn)
This is the structure so far: spotlight/ pom.xml (parent pom) spotlight-graph/ Graph API, not used yet on this osgi issue spotligh-core/ (this is the web project) servlet-1.0.1.jar (this is a build of the latest equinox HTTPService, we install in our local repository in order to use it) Inside spotlight-core, for now we decided to put all our bundles inside web-inf/resources/bundles, so all libs are packed not referenced by maven (yet) Ok, as the spotlight core, we tried the same approach as sling: OSLServlet is the servlet that should repond on /config and than delegate to the web console, this servlet creates a class named OSL (more bellow) and creates the HttpServiceServlet and configures it as well. OSL is the class responsible to startup felix, it's also a BundleActivator, and we use a BootstrapInstaller (from sling) to start and install all bundles, the BootstrapInstaller is a BundleActivator. As I mentioned, from what I've seen, everything goes normal, but the HTTPServiceTracker of the webconsole never gets fired, don't know why. So the ProxyServlet from equinox never gets a registration, and always send an HttpError as response. Using Pax-Web, the webconsole Tracker gets called, but, I have no delegate servlet (don't know how to do it) Well, thanks very much for the help, If you need any other information please let us know. We are very, very happy with your help Best regards On Wed, Jan 21, 2009 at 6:13 PM, Karl Pauls <[email protected]> wrote: > Well, can you make your project available someplace so that we can > have a look at what is going wrong exactly? > > regards, > > Karl > > On Wed, Jan 21, 2009 at 8:10 PM, Vinicius Carvalho > <[email protected]> wrote: > > Hello there! We are almost giving up on OSGi since we can not find how to > > get the webconsole running. It's a real pain to get it working inside a > > servlet container. We've debugged the entire sling app and it works as a > > charm (although it uses older versions of all libs). I really can't > imagine > > why after my HttpServiceServlet gets started and register itsefl as and > > HTTPService service in the context the ServiceTracker of the webconsole > is > > not triggered. > > > > We tried to replace equinox httpservice by pax-web, and the Tracker this > > time gets notified but, we could not access the console since there's no > > servlet to delegate the service. We are still checking this, I wish I > could > > use the embedded version of containers like tomcat and jetty, the way > spring > > DM does, or even use spring dm server, but unfortunatelly we need to be > able > > to deploy on any container, and this is my last week, if that does not > work, > > we might drop OSGi and use another approach to build our modules. > > > > Anyone got another idea that could help us? > > > > Regards > > > > On Tue, Jan 20, 2009 at 3:47 PM, Vinicius Carvalho < > > [email protected]> wrote: > > > >> Well, Sling uses Felix 1.0.4 right? I'm running my tests with 1.4.1 and > >> also I have a newer version of the equinox. After running sling on debug > >> mode here I found that the source I have for the equinox server api is > not > >> the same. I wonder if this is the problem. One difference I have is the > >> props.put(EMBEDDED_EXECUTION_PROP, "true"); since it seems that it does > not > >> exist anymore. > >> > >> > >> On Tue, Jan 20, 2009 at 2:15 PM, Vinicius Carvalho < > >> [email protected]> wrote: > >> > >>> Well, I'm still trying here to get it working. As for using Sling, > well, > >>> if we could use just the launcher that would be one ideia, but we > really > >>> would not like to have the whole sling application just to use > web-console. > >>> Although we will need a JCR repository in our app, I don't think we > should > >>> have sling embedded . > >>> > >>> Regards > >>> > >>> On Tue, Jan 20, 2009 at 1:44 PM, Carsten Ziegeler < > [email protected]>wrote: > >>> > >>>> Vinicius Carvalho wrote: > >>>> > Well, The Activator is receiving the System bundlecontext where the > >>>> > webconsole gets its own bundlecontext. When we register a service > >>>> tracker it > >>>> > tracks services only for the specific bundle? could this be the > >>>> problem? > >>>> > > >>>> This is correct, the service tracker tracks all services regardless > from > >>>> which bundle > >>>> they're comming. > >>>> > >>>> I've no idea what goes wrong in your case, but why are you not just > >>>> using the Sling Webapp? I has nearly no overhead and provides you with > a > >>>> usuable setup. Or you can use the standalone jar from Sling. > >>>> > >>>> Carsten > >>>> > >>>> > >>>> -- > >>>> Carsten Ziegeler > >>>> [email protected] > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: [email protected] > >>>> For additional commands, e-mail: [email protected] > >>>> > >>>> > >>> > >> > > > > > > -- > Karl Pauls > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
