Hi Simon,
You were right.! There was a javax.servlet bundle in my osgi runtime, as well as a servlet-api.jar in my webapps shared library folder, which must have caused this issue. However I find that my problem does not go away. The on
I will be out of the office starting 2010-06-09 and will not return until
2010-06-12.
I will be out of the office from Jun.9 to Jun 12, call 13917851703 if any
emergency. If you cannot reach me, I must be in some place without signal.___
equinox-dev ma
Hi Srijith,
This sort of error happens when you have more than one provider of the
Servlet API. In this case your application is binding to a different
exporter of the Servlet API than what's being used by Jetty. It's usually
simplest to just have the one javax.servlet bundle exporting the Servlet
As discussed in today's architecture call, HEAD is now open for
development towards the Indigo release for the Eclipse and Equinox
projects.
To recap how this works, org.eclipse.releng will not be tagged with R3_6
until we officially declare 3.6. At that point org.eclipse.releng will be
branc
See http://wiki.eclipse.org/index.php/Context_Class_Loader_Enhancements
Tom
|>
| From: |
|>
>--|
|Scott Lewis
Hi,
Would someone be able to point me at docs on the context classloader
support specifics in Equinox?
Thanks,
Scott
___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
Hi,
I have a webApp which I am deploying with Equinox Jetty Server. It works
fine, however at times, when I stop and start the application, I get the
following exception and my Application is then not accessible.
2010-06-09 15:18:35.014:/MyWebApp:WARN: unavailable
javax.serv
