You've got a lot going on here. I'm not sure I can directly address your questions, but I can provide a simplified example of how I'm resolving XSLT views in my application.
First, I've got a urlMapping bean just like you've configured below. The mappings point to another bean (presumably a bean, such as a controller, that can handle a request).
The controller below extends org.springframework.web.servlet.mvc.SimpleFormCont roller. The formView property is just a string that the ViewResolver will use to look up the actual view class.
<bean id="urlMapping" class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
I'm using a ResourceBundleViewResolver in my set-up. It looks for the file views.properties (where the views part is set with the basename property) on the classpath. It uses the view name specified in the controller to look up the corresponding view class that will do the actual rendering of the model. InternalResourceViewResolver, on the other hand, tries to resolve the view from the path that its given. It doesn't use views.properties.
<bean id="myForm" class="com.thatone.web.MyForm" lazy-init="true">
My views.properties looks something like this. The XsltViewImpl class is an extension of AbstractXsltView.
<bean id="viewResolver" class="org.springframework.web.servlet.view.ResourceBundleViewResolver">
I hope this helps.
- Justin Makeig