I said I reproduced your bug in another context by placing the dragIndicator in a treeNode. This is not really true, because in my case it was a javascript error with a very similar description. But for me the rest of the side works, in your case the whole page is replaced by this xml error message.

Well, it was about time, that is a good workaround. But even so the script is not rendered as in the examples, having CDATA block around it. And because of the new content type I had trouble with the form-based authentication in tomcat. I use a JDBCRealm to authenticate the users based on their roles and when I changed the view's content type it stopped working. I figured out how to deal with it anyway. Thanks for the great tip!