application context overload! portlet/DWR/etc

[shan]

my scenario:

I am developing a series of portlets using the Spring Portlet MVC (deployed in Liferay->Tomcat).
Most of these portlets make use of DWR as well - but since there is no straight forward way to use the pure DWR/MVC solution in a portal environment, each portlet (in its web.xml) declares a DwrSpringServlet to receive all the AJAX requests.

So now this servlet will start up its own context, in addition to the context the DispatcherPortlet starts - so now, each "portlet" as a whole has two parallel contexts; multiply this by the number of total portlets, and that's a crap load of inefficiency (service classes, etc)

My question is, on the topic of SHARING APPLICATION CONTEXTS across webapps, is this still the standard way?
http://springtips.blogspot.com/2007/...n-context.html

or is there a something in 2.5 that simplifies this or offers a new mechanism? thanks!

[sravankumar4rmhyd]

Hi, Can you please share working project includes Spring and DWR on Liferay Portlets.

Thanks in advance