Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
爱吃血肠
spring-framework
提交
626a5fe4
S
spring-framework
项目概览
爱吃血肠
/
spring-framework
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
S
spring-framework
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
626a5fe4
编写于
8月 13, 2014
作者:
J
Juergen Hoeller
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
BeanNameViewResolver ignores non-View beans
Issue: SPR-12079
上级
887815f4
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
30 addition
and
19 deletion
+30
-19
spring-webmvc/src/main/java/org/springframework/web/servlet/view/BeanNameViewResolver.java
...pringframework/web/servlet/view/BeanNameViewResolver.java
+30
-19
未找到文件。
spring-webmvc/src/main/java/org/springframework/web/servlet/view/BeanNameViewResolver.java
浏览文件 @
626a5fe4
/*
* Copyright 2002-201
2
the original author or authors.
* Copyright 2002-201
4
the original author or authors.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
...
...
@@ -26,25 +26,24 @@ import org.springframework.web.servlet.View;
import
org.springframework.web.servlet.ViewResolver
;
/**
*
Simple implementation of ViewResolver that interprets a view name
*
as bean name in the current application context, i.e. in the XML
*
file of the executing DispatcherServlet
.
*
A simple implementation of {@link org.springframework.web.servlet.ViewResolver}
*
that interprets a view name as a bean name in the current application context,
*
i.e. typically in the XML file of the executing {@code DispatcherServlet}
.
*
* <p>This resolver can be handy for small applications, keeping all
* definitions ranging from controllers to views in the same place.
* For normal applications, XmlViewResolver will be the better choice, as
* it separates the XML view bean definitions into a dedicated views file.
* View beans should virtually never have references to any other
* application beans - such a separation will make this clear.
* <p>This resolver can be handy for small applications, keeping all definitions
* ranging from controllers to views in the same place. For larger applications,
* {@link XmlViewResolver} will be the better choice, as it separates the XML
* view bean definitions into a dedicated views file.
*
* <p>
This ViewResolver does not support internationalization.
*
Consider ResourceBundleViewResolver if you need to apply different
* view resources per locale.
* <p>
Note: Neither this {@code ViewResolver} nor {@link XmlViewResolver} supports
*
internationalization. Consider {@link ResourceBundleViewResolver} if you need
*
to apply different
view resources per locale.
*
* <p>Note: This ViewResolver implements the Ordered interface to allow for
* flexible participation in ViewResolver chaining. For example, some special
* views could be defined via this ViewResolver (giving it 0 as "order" value),
* while all remaining views could be resolved by a UrlBasedViewResolver.
* <p>Note: This {@code ViewResolver} implements the {@link Ordered} interface
* in order to allow for flexible participation in {@code ViewResolver} chaining.
* For example, some special views could be defined via this {@code ViewResolver}
* (giving it 0 as "order" value), while all remaining views could be resolved by
* a {@link UrlBasedViewResolver}.
*
* @author Juergen Hoeller
* @since 18.06.2003
...
...
@@ -63,7 +62,7 @@ public class BeanNameViewResolver extends WebApplicationObjectSupport implements
@Override
public
int
getOrder
()
{
return
order
;
return
this
.
order
;
}
...
...
@@ -71,7 +70,19 @@ public class BeanNameViewResolver extends WebApplicationObjectSupport implements
public
View
resolveViewName
(
String
viewName
,
Locale
locale
)
throws
BeansException
{
ApplicationContext
context
=
getApplicationContext
();
if
(!
context
.
containsBean
(
viewName
))
{
// Allow for ViewResolver chaining.
if
(
logger
.
isDebugEnabled
())
{
logger
.
debug
(
"No matching bean found for view name '"
+
viewName
+
"'"
);
}
// Allow for ViewResolver chaining...
return
null
;
}
if
(!
context
.
isTypeMatch
(
viewName
,
View
.
class
))
{
if
(
logger
.
isDebugEnabled
())
{
logger
.
debug
(
"Found matching bean for view name '"
+
viewName
+
"' - to be ignored since it does not implement View"
);
}
// Since we're looking into the general ApplicationContext here,
// let's accept this as a non-match and allow for chaining as well...
return
null
;
}
return
context
.
getBean
(
viewName
,
View
.
class
);
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录