Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
爱吃血肠
spring-framework
提交
bf4b9f5f
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,发现更多精彩内容 >>
提交
bf4b9f5f
编写于
8月 07, 2010
作者:
C
Chris Beams
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Replace 'Java EE' with 'enterprise Java' as appropriate
Also change 'JEE' -> 'Java EE'
上级
06259900
变更
5
隐藏空白更改
内联
并排
Showing
5 changed file
with
25 addition
and
25 deletion
+25
-25
spring-framework-reference/src/aop.xml
spring-framework-reference/src/aop.xml
+6
-6
spring-framework-reference/src/beans.xml
spring-framework-reference/src/beans.xml
+2
-2
spring-framework-reference/src/transaction.xml
spring-framework-reference/src/transaction.xml
+2
-2
spring-framework-reference/src/web-integration.xml
spring-framework-reference/src/web-integration.xml
+14
-14
spring-framework-reference/src/xsd-configuration.xml
spring-framework-reference/src/xsd-configuration.xml
+1
-1
未找到文件。
spring-framework-reference/src/aop.xml
浏览文件 @
bf4b9f5f
...
...
@@ -74,9 +74,9 @@
<listitem>
<para><emphasis>
Aspect
</emphasis>
: a modularization of a concern
that cuts across multiple classes. Transaction management is a good
example of a crosscutting concern in
Java EE applications. In Spring
AOP, aspects are implemented using regular classes (the
<link
linkend=
"aop-schema"
>
schema-based approach
</link>
) or regular
example of a crosscutting concern in
enterprise Java applications.
In Spring AOP, aspects are implemented using regular classes (the
<link
linkend=
"aop-schema"
>
schema-based approach
</link>
) or regular
classes annotated with the
<interfacename>
@Aspect
</interfacename>
annotation (the
<link
linkend=
"aop-ataspectj"
><interfacename>
@AspectJ
</interfacename>
...
...
@@ -211,7 +211,7 @@
<para>
Spring AOP is implemented in pure Java. There is no need for a
special compilation process. Spring AOP does not need to control the
class loader hierarchy, and is thus suitable for use in a
Java EE web
class loader hierarchy, and is thus suitable for use in a
Servlet
container or application server.
</para>
<para>
Spring AOP currently supports only method execution join points
...
...
@@ -235,8 +235,8 @@
efficiently with Spring AOP, such as advise very fine-grained objects
(such as domain objects typically): AspectJ is the best choice in such
cases. However, our experience is that Spring AOP provides an excellent
solution to most problems in
Java EE applications that are amenable to
AOP.
</para>
solution to most problems in
enterprise Java applications that are
amenable to
AOP.
</para>
<para>
Spring AOP will never strive to compete with AspectJ to provide a
comprehensive AOP solution. We believe that both proxy-based frameworks
...
...
spring-framework-reference/src/beans.xml
浏览文件 @
bf4b9f5f
...
...
@@ -5206,8 +5206,8 @@ public @interface MovieQualifier {
<para>
Spring also supports injection using the JSR-250
<interfacename>
@Resource
</interfacename>
annotation on fields or bean
property setter methods. This is a common pattern in Java EE 5 and
Java
6, for example,
in JSF 1.2 managed beans or JAX-WS 2.0 endpoints. Spring
property setter methods. This is a common pattern in Java EE 5 and
6,
for example
in JSF 1.2 managed beans or JAX-WS 2.0 endpoints. Spring
supports this pattern for Spring-managed objects as well.
</para>
<para><interfacename>
@Resource
</interfacename>
takes a name attribute,
...
...
spring-framework-reference/src/transaction.xml
浏览文件 @
bf4b9f5f
...
...
@@ -169,8 +169,8 @@ TR: OK AS IS - I think it's fine as is - the concepts apply to both programmatic
management?
</title>
<para>
The Spring Framework's transaction management support changes
traditional rules as to when a
Java EE application requires an
application server.
</para>
traditional rules as to when a
enterprise Java application requires
a
n a
pplication server.
</para>
<para>
In particular, you do not need an application server simply for
declarative transactions through EJBs. In fact, even if your
...
...
spring-framework-reference/src/web-integration.xml
浏览文件 @
bf4b9f5f
...
...
@@ -607,19 +607,19 @@
</para>
<para>
While Spring has its own
<link
linkend=
"mvc"
>
powerful web
layer
</link>
, there are a number of unique advantages to building a
Java EE
application using a combination of Tapestry for the web user interface and
the Spring container for the lower layers. This section of the web
integration chapter attempts to detail a few best practices for combining
these two frameworks.
</para>
<para>
A
<emphasis>
typical
</emphasis>
layered
Java EE application built with
Tapestry and Spring will consist of a top user interface (UI) layer built
with Tapestry, and a number of lower layers, all wired together by one o
r
more Spring containers. Tapestry's own reference documentation contains
the following snippet of best practice advice. (Text that the author of
this Spring section has added is contained within
<literal>
[]
</literal>
brackets.)
</para>
layer
</link>
, there are a number of unique advantages to building a
n
enterprise Java application using a combination of Tapestry for the web
user interface and the Spring container for the lower layers. This section
of the web integration chapter attempts to detail a few best practices for
combining
these two frameworks.
</para>
<para>
A
<emphasis>
typical
</emphasis>
layered
enterprise Java application
built with Tapestry and Spring will consist of a top user interface (UI)
layer built with Tapestry, and a number of lower layers, all wired togethe
r
by one or more Spring containers. Tapestry's own reference documentation
contains the following snippet of best practice advice. (Text that the
author of this Spring section has added is contained within
<literal>
[]
</literal>
brackets.)
</para>
<para>
<quote>
...
...
@@ -1092,7 +1092,7 @@ public abstract class Login extends BasePage implements ErrorProperty, PageRende
are coming from, and in fact it is easy to slip in another implementation,
for example, during testing. This inversion of control is one of the prime
goals and benefits of the Spring Framework, and we have managed to extend
it
all the way up the Java EE
stack in this Tapestry application.
</para>
it
throughout the
stack in this Tapestry application.
</para>
</section>
</section>
...
...
spring-framework-reference/src/xsd-configuration.xml
浏览文件 @
bf4b9f5f
...
...
@@ -466,7 +466,7 @@ public class Client {
</section>
<section
id=
"xsd-config-body-schemas-jee"
>
<title>
The
<literal>
jee
</literal>
schema
</title>
<para>
The
<literal>
jee
</literal>
tags deal with JEE (Java Enterprise Edition)-related
<para>
The
<literal>
jee
</literal>
tags deal with J
ava
EE (Java Enterprise Edition)-related
configuration issues, such as looking up a JNDI object and defining EJB references.
</para>
<para>
To use the tags in the
<literal>
jee
</literal>
schema, you need to have
the following preamble at the top of your Spring XML configuration file;
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录