《【精品文档】519关于计算机专业App设计优化的毕业设计论文英文英语外文文献翻译成品资料：运用Spring框架进行快速的开源J2EE Web应用程序开发：一个案例研究（中英文双语对照）》由会员分享，可在线阅读，更多相关《【精品文档】519关于计算机专业App设计优化的毕业设计论文英文英语外文文献翻译成品资料：运用Spring框架进行快速的开源J2EE Web应用程序开发：一个案例研究（中英文双语对照）（22页珍藏版）》请在金锄头文库上搜索。
1、本文是中英双语对照毕业设计论文外文文献翻译，下载之后无需调整复杂的格式直接可用！一辈子也就一次的事！外文标题：Spring Framework for rapid open source J2EE Web Application Development: A case study外文作者：John Arthur,Shiva Azadegan 文献出处: Proceedings of the Sixth International Conference on Software Engineering, Artificial Intelligence, Networking and Paralle
2、l,2019 (如觉得年份太老，可改为近2年，毕竟很多毕业生都这样做)英文2684单词，17894字符(字符就是印刷符)，中文4324汉字。（如果字数多了，可自行删减，大多数学校都是要求选取外文的一部分内容进行翻译的。）Spring Framework for rapid open source J2EE Web Application Development: A case studyAbstract: In the highly competitive arena of web application development, it is important to develop the
3、application as accurately, economically, and efficiently as possible. One way to increase productivity is to decrease complexity. This has been an underlying theme in a recent movement to change the way programmers approach developing Java 2 Platform, Enterprise Edition (J2EE) web applications. The
4、focus of the change is how to create J2EE-compliant software without using Enterprise Java Beans (EJB). The foremost alternative is the Spring Framework, which provides less services but it is much less intrusive than EJB. The driving force behind this shift is the need for greater productivity and
5、reduced complexity in the area of web application software development and implementation. In this paper we briefly describe Spring underlying architecture and present a case study using Spring.IntroductionDue to the fundamental nature of the softwares architecture, the choice of architecture usuall
6、y has the greatest impact on productivity compared to any other individual aspect of software development (1). One of the best ways to increase productivity is to find the simplest architecture which fulfills the needs of the client, while still providing the desired requirements of J2EE architectur
7、e. The core building blocks for any J2EE application are the presentation layer (User Interface, UI, tier), the business services layer (Middle tier), and the data access layer (Enterprise Information Systems, EIS, tier). These three layers need to be implemented at the bare minimum to be considered
8、 J2EE compliant. A number of systems also include a persistence layer as part of the business services layer.EJB ArchitectureThe Local EJB architecture is shown in Figure 1. As previously mentioned, the three layers are presented: the UI tier, the Middle tier, and the EIS tier. The UI tier is normal
9、ly supplied by a Model-View-Controller (MVC) framework. The business layer is provided by “business methods” interfaces that the web tier objects can directly access without having to use the EJB APIs. The business objects are stateless session beans with local interfaces, running inside an EJB cont
10、ainer, and will provide transaction management, thread management, and role-base security. All data access will be through entity beans in the “classic” J2EE architecture. Container Managed Persistence (CMP) entity beans are regarded as the best choice. Java Transaction API (JTA) accessed through th
11、e EJB container provides transaction coordination to the EIS tier. Lightweight container architecture As illustrated in Figure 2, the lightweight container also uses an MVC framework to implement the web tier. The Spring framework can use a dedicated web framework such as Struts or WebWork , or can
12、be managed by the lightweight container to integrate closely with the business objects. All the business objects are Plain Old Java Objects (POJOs) running inside the lightweight container. The lightweight container provides enterprise services by invoking an Aspect-Oriented Programming (AOP) Interc
13、eptor. This way it can transparently weave additional behavior before or after business method execution 1. Since lightweight containers rely on AOP interceptors, there is no need to depend upon the container APIs, and therefore, they are usable outside any container.Figure 1 - Local EJB architectur
14、e presenting all three core building blocks (1)For the best results, the business objects should be accessed exclusively though their interfaces. Data Access can use either JDBC or a lightweight Object/Relational (O/R) mapping layer to provide transparent persistence. The EIS tier is the same as the
15、 Local EJB EIS tier.Spring Framework.The goal is to produce web application software accurately, economically, and efficiently, it is important to emphasize a number of objectives: simplicity, testability, and portability. The simpler it is to develop and maintain code, the more cost effective the p
16、roject will be over the long run. EJBs are very complex and require an EJB container, which translates into the need for a high-end application server. The necessity of an application server also adds to the administrative complexity of using EJBs 2. The lightweight container only requires a servlet engine. This also addresses the issue of portability. EJBs are written specifically for EJB containers and rely heavily on the EJB APIs. Due to the no
