 Spring Framework 1.1.5 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 57 页 | 166.71 KB | 1 年前3 Spring Framework 1.1.5 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 57 页 | 166.71 KB | 1 年前3
 Spring Framework 1.2.0 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 67 页 | 194.16 KB | 1 年前3 Spring Framework 1.2.0 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 67 页 | 194.16 KB | 1 年前3
 Spring Framework 1.2.2 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 72 页 | 205.76 KB | 1 年前3 Spring Framework 1.2.2 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 72 页 | 205.76 KB | 1 年前3
 Spring Framework 1.2.1 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 69 页 | 197.87 KB | 1 年前3 Spring Framework 1.2.1 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 69 页 | 197.87 KB | 1 年前3
 Spring Framework 1.2.3 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 74 页 | 215.40 KB | 1 年前3 Spring Framework 1.2.3 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 74 页 | 215.40 KB | 1 年前3
 Spring Framework 1.2.5 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 79 页 | 226.37 KB | 1 年前3 Spring Framework 1.2.5 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 79 页 | 226.37 KB | 1 年前3
 Spring Framework 1.2.4 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 77 页 | 223.73 KB | 1 年前3 Spring Framework 1.2.4 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 77 页 | 223.73 KB | 1 年前3
 Spring Framework 1.2.7 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 87 页 | 248.22 KB | 1 年前3 Spring Framework 1.2.7 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 87 页 | 248.22 KB | 1 年前3
 Spring Framework 1.2.6 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 83 页 | 236.45 KB | 1 年前3 Spring Framework 1.2.6 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 83 页 | 236.45 KB | 1 年前3
 Spring Framework 1.2.8 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 89 页 | 254.65 KB | 1 年前3 Spring Framework 1.2.8 ChangelogDispatcherServlet does not override "doHead" anymore, leveraging HttpServlet's default "HEAD" handling via "doGet" * factored out protected "resolveViewName" method from DispatcherServlet's "render" implementation not start with the application's context path (rather unusual) * fixed FrameworkServlet to use "doGet"/"doPost"/"doHead" etc, to reenable proper LastModified support in controllers * fixed DispatcherServlet's0 码力 | 89 页 | 254.65 KB | 1 年前3
共 14 条
- 1
- 2














