Seeing this thread on DWR mailing list, I thought I’d post one way to deal with DWR response. The actual problem was initiated by someone asking what’s the best way to display status messages to users using DWR.
A while ago I was asked to take a WiFi router and add some bell and whistles to its interface. It was one of those small NAT boxes – nothing more than a LAN switch and a WLAN access point strapped to a 200 MHz system-on-a-chip running Linux. ucLinux, to be exact.
I recently stumbled across a NotSerializableException in the project I was working, and I decided to share this experience with you because the cause of the problem it’s quite interesting and some of you might come across the same problem.
Spring allows chaining of multiple view resolvers. However, there are some view resolvers like the ones extending UrlBasedViewResolver which must be the last in the chain, hence the limitation of having only one such view resolver in your chain.