DWR

Jose,

The mappings are currently:

Map<String, Object> mappings = new HashMap<String, Object>();
mappings.put("/engine.js", handler);
mappings.put("/util.js", handler);
mappings.put("/interface/**", handler);
mappings.put("/call/**", handler);
mappings.put("/test/**", handler);
mappings.put("/download/**", handler);

If we change the mappings to:
<prop key="/dwr/*/">dwrController</prop>

In order for this to work we need to call setAlwaysUseFullPath(true); in DwrHandlerMapping.

Is there a problem with this approach?

You would be forcing a specific mapping for the servlet in web.xml which is undesired. The best solution I can come with is to name the test page dwr-test.html or something like that instead of index.html (a mapping I'm hesitant to add).

Jose if the proposed solution is OK with you, I can get this change in if you are busy.

This is the easiest way I've come across. In addition to being mapped at /app/dwr/index.html it's mapped at /app/dwr/test/index.html. Outside Spring both urls work, inside Spring just the later (when using <dwr:url-mapping /> of course).

The solution is not pretty but there's no better alternative IMHO. The problem is inherited from DWR core where URLs like index.html or /test/ aren't avoided. This works fine as long as DWR serves everything but becomes problematic when the servlet is shared (as is with SpringMVC).

I'm not committing anything though. And I would raise another issue to sandbox this problem using a proprietary namespace (which would be real solution but requires consensus)