I have downloaded rsp03 and am having some issues. When I attempt to run Equinox Http, I get the following error message:

"Could not load tomcat server configuration at \Servers\Tomcat v5.5\Server @ localhost-config. The configuration by be corrupt or incomplete."

I setup (at least I think I did) the proper JRE for my environment. Any assistance would be greatly appreciated.
Jason

What I might find pretty cool would be a running a JSF based web application which defines the workbench (as components which manage other components) and is upgradeable by third party people who can simpy connect via an extension point to the main JSF apps workbench parts.
Is there a project out there already doing this?

-clem

You mention that you are already using an OSGI implementation that lets you deploy under a web container, and still use filters, jsp etc. Could you tell me which OSGI implementation you are using, and how you are mapping your servlet and filter classes from the web.xml definitions to the classes stored in osgi bundles?

We currently use OSGI bundles for our web application. We don't use the Eclipse implementation. For the moment we have some code that manages the classloader to allow our application to run under Tomcat using servlets, JSPs, filters etc. The problem of course arises when you need to integrate with client systems that aren't the container you have complete control over.

The reality is that large organisations running on a J2EE infrastructure would like to deploy your application to that container. They're not going to consider altering (launching their container from OSGI) the infrastructure that their many applications currently run on. Their containers provide functionality that they value. I have yet to see a generic solution allowing an OSGI based applications to be used in a web application container transparently. It's a bit frustrating.

Reason for Equinox:
- the tools (dependency checking etc) that come with it.
- the fact that you can easily reuse non-ui plug-ins that already exist.
- the fact that it bridges J2EE webapp with OSGi; you can use OSGi bundles WITHIN an existing webapp, mix and match; though of course the
long-term vision is to do away with the J2EE container and run in a native OSGi container; Felix is a great candidate.
Known reasons to avoid:
- None, really. current need for JSP precompilation seems to be the biggest bone of contention, but it will be resolved very shortly. Though JSP is not the only rendering possibility (cf. Wicket et al.).
Rgds,
Wolfgang

Hi,

that's really fascinating!
I started using OSGI several weeks ago and also think it's a good (better) way to manage webapps and other server-side stuff.
Is there any reason why you've choosen Eclipse/Equinox as OSGI implementation?
It's really cool to embed the servlet container (and other typical server-side components) and run it inside osgi. I've read about someone who even embedded an EJB container.

Do you have any experiences about running OSGI that way in a longer term - for weeks and months?
Is there any known reason to avoid using OSGI on server-side at all?

Cheers,
Rainer

This thread is to discuss the article "Developing Eclipse/OSGi component webapps" and its questions raised at http://www.infonoia.com/en/content.jsp?d=inf.05.09 .