Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » Undelopying a Spring MVC bundle also leads to undeploying the other bundles(Using the DispacherServlet results in undeploying problem)
Undelopying a Spring MVC bundle also leads to undeploying the other bundles [message #1731165] Tue, 03 May 2016 09:42
Vlad Muresan is currently offline Vlad MuresanFriend
Messages: 1
Registered: May 2016
Junior Member
I have a Spring MVC app configured as in the files from attached archive.

Everything works fine, but when I undeploy the bundle, the other bundles are also undeployed. (The "DELETE" action is detected and this leads to the entire undeploy process). This is a huge overhead for me as it leads to huge amount of waiting time.

There's also a workaround, using "UNINSTALL" action which doesn't trigger the other bundle to undeploy.

I suspect there's an issue with the DispacherSerlvet configuration (if I remove the servlet from web.xml the undeploy works fine).

In some recipes I saw `` is used instead of `` but I'm having troubles deploying the `spring-osgi-web` dependencies, and on the local environment I have a strange error that sounds like this:

`HTTP Status 500 - Request processing failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [javax.servlet.http.HttpServletRequest]: Specified class is an interface`

Have you encountered such an issue or can you advise otherwise?

Thank you!

P.S. the commented parts are the ones related to the spring-osgi-web dependencies. I also added the entire error stacktrace for that.
Previous Topic:From OSGi to Blueprints & Virgo?
Next Topic:How do I configure SPNEGO authentication?
Goto Forum:

Current Time: Tue Jun 15 11:17:25 GMT 2021

Powered by FUDForum. Page generated in 0.01694 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top