Hello,

  I've been rapidly learning the ins & outs of OSGi and was wondering if any 
others were in similar situations as we are.  We are re-architecting an 
existing web based system using an OSGI based framework.  We currently create 
an ear file that is deployed to a JBoss server.  We are moving an architecture 
where we deploy bundles to an OSGi framework.

I have an existing Felix 2.0.1 installation and have tried (unsuccessfully) to 
deploy Glassfish V3 using Sahoo's embeddedgf 
activator<http://weblogs.java.net/blog/ss141213/archive/2010/02/14/how-embed-glassfish-existing-osgi-runtime>.
  It installs all of the bundles and seems to start some of them, but there 
seems to be some unresolved dependencies, and the domain doesn't start up.  Has 
anyone tried this with any success?

My next approach was to simply start up Glassfish, then use the Felix framework 
that Glassfish starts up.  I have dropped the Felix Web Console bundles in the 
autodeploy directory and everything starts up fine - I can access the domain 
root page, the GF Admin console, and the Felix Web Console.  I was curious to 
see what other's opinions were as to this scenario in a production environment 
(starting up GF and using its Felix, as opposed to starting up Felix, then 
deploying GF to it).

We are looking at Glassfish vs. something lightweight like Jetty or Tomcat for 
a couple of reasons: we will be using JMS and JDBC datasources, and more 
importantly Glassfish V3 has been approved and accredited for the system we 
will be deploying to.

Thanks,
 Larry

Reply via email to