Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

changed J2EE to Java EE

Browse Source
This commit is contained in:
Thomas Risberg
2009-07-30 18:32:05 +00:00
parent 40c4941cbf
commit 4bf3a9c9bd
9 changed files with 37 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
spring-framework-reference/src/aop.xml
View File

@@ -74,7 +74,7 @@
<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 J2EE applications. In Spring
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
classes annotated with the <interfacename>@Aspect</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 J2EE web
class loader hierarchy, and is thus suitable for use in a Java EE web
container or application server.</para>
<para>Spring AOP currently supports only method execution join points
@@ -235,7 +235,7 @@
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 J2EE applications that are amenable to
solution to most problems in Java EE applications that are amenable to
AOP.</para>
<para>Spring AOP will never strive to compete with AspectJ to provide a