Tomcat/jetty path compatibility issues between containers

Source: Internet
Author: User

When using the SPRINGMVC framework in a project, the view path string returned in the Controller method is finally consolidated with the configuration path in the XML file configuration, resulting in a completed view file path. Then there's a problem with the difference between Tomcat and jetty:

<bean id= "Internalviewresolver" class= "Org.springframework.web.servlet.view.InternalResourceViewResolver"        p:viewclass= "Org.springframework.web.servlet.view.JstlView"        p:prefix= "/web-inf/view/jsp"        p:suffix = ". jsp"        p:order= "1"/>





Tomcat in view file/web-inf/view/jsp//default/ui/user/update_passwd.jsp can be found

And in the Jetty view file /web-inf/view/jsp//default/ui/user/update_passwd.jsp can not be found, remove superfluous/rear can find, jetty for path specification more stringent?

Tomcat/jetty path compatibility issues between containers

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.