XX 学
学生毕业设计（文）外文译文
学生姓名：
学号：
专业名称：电子商务
译文标题（中英文）：定义开发J2EE Web信息系统方法（Defining methodologies for developing J2EE webbased information systems）
译文出处：Elsevier ScienceDirect全文期刊数库
指导教师审阅签名：
外文译文正文：
摘：
文介绍基Java开发项目框架概念背景介绍开发IT项目开发框架产生许设计开发工作正方式重复总佳实践相致已确定企业交付应设计模式工具效解决方案现开发框架提供：（1）应开发堆栈户界面数整合（2）提高利框架基础设施相关技术体系结构该体系结构定义开发方法目协助户开发项目
1 介绍
软件工具复杂空间系统分析越越应Web户界面实现基网络台科学分析模拟结果分布科学家间信息交换实时基Web访问非线性分析模拟软件成许应系统关键部分强化技术改变网络硬件软件提供更选择WEB台合理选择发展非线性分析整区日益增加重性众应网站目前发展阶段特点量开源框架出现框架式Web开发重点转移更高水基功重提高开发效率
某情况开源框架没提供解决常见问题方法开发商建立开发框架顶部开源框架文目描述基Java开发框架利开源框架协助开发基Web应程序通现开源框架文提出种新体系结构提高利框架基础设施相关技术该架构定义开发方法目协助项目定制开发集成项目
常见应设计问题项目独特功求常模式情况身设计开发利文介绍种定制框架直努力寻找样常见应问题确定设计模式开发商开发框架称发达XYZ框架提供套模式工具建立行业佳实践针常见应问题提供应开发堆栈表现集成层文阐述应问题模式工具行业佳实践开发框架定制XYZ种工程需开发配置基框架工具StrutsSpringHibernateJUnit
2 开发框架技术
21 代码层配置分离
Web应程序设计问题介绍业务逻辑数访问安全分离设计问题分代码层具优点：易维护实现良设计模式力够选择专门工具技术具体问题分离成项目层导致层间赖关系例案例涉简单数录入查询通常必须整合显示业务逻辑数访问起提供需功必须良定义策略理赖关系XYZ框架相结合开发设计模式重代码配置文件容易该框架采控制弹簧反转理赖性Spring框架[提供种方式联系起构成应程序象实现目标Spring应程序文理象间赖关系策略Spring赖注入方法拦截技术介绍
写代码赖象负责创建象会导致紧耦合希代码松散耦合赖注入种技术帮助完成赖注入种形式控制反转（IoC）应程序赖注入代码变更干净更容易理解松散耦合允许更容易配置测试XYZ框架采Spring应文文件定义层层间赖关系方法拦截面方面编程（AOP）概念通JDK动态代理Spring AOP实现方法拦截XYZ框架Spring AOP理等问题事务理性监测
开发XYZ框架两部分组成：代码配置代码驻留特定应层集中特定应解决方案数库交互提交数屏幕结构胶种应层代码分离配置允许独立理结构配置相代码库灵活性例数访问象（DAO）实现知道通数源JDBC连接数库知道数源执行什Java命名目录接口（JNDI）文驱动程序理器指远程数库数库数源里道实施数源操作方式样服务象赖道知道刀通HibernateJDBC实现直Web服务服务象相方式道相互作DAO实现
Spring提供种通Spring应文理应程序整结构组XML文件定义文件中定义应程序文然较文件组中定义简化配置理样应程序文文件形成完整应程序配置逻辑集合称配置集
开发基Java企业应程序标准配置框架配置设置外部资源数源JNDI资源种类型配置时产生问题：（1）完整数库尚未加载开发商想测试某类型数显示果基础数库尚未完成够样做（2）服务道没开发出结合未完成服务DAO停止发展
问题降低生产效率开发XYZ框架已代码分离结构配置设置专门针发展减轻担心外部系统性解决眼前发展关需求
开发XYZ框架定义两配置设置：默认独立定义应程序添加基项目需额外配置集默认配置设置连接定义JNDI DataSource开发数库充分开发应服务道独立配置集发展灵活环境配置集：（1）连接安装数库DriverManagerDataSource开发数库（2）弹簧方DataSourceTransactionManager事务理（3）充分利开发应服务道（4）完全线Spring应程序文运行测试完全应服务器外面
开发框架XYZ应文配置应程序文XML文件中定义配置集组XML文件定义应程序文配置集分两部分：服务Web服务部分定义服务DAO资源服务整合层Web部件定义表示层组件配置集没两部分完整
开发XYZ框架配置集调bean引文件定义分组applicationcontextmappingproperties beanrefcontextxmlbeanrefcontextxml文件定义配置服务集文件位服务项目src 配置目录配置设置应程序文间享文件位目录外配置子目录中包含特定文件例服务道间配置设置享时支持服务（数源）属子目录XML文件定义弹簧豆应中MathML查源〈bean〉标签Spring bean创建应程序文初始化Java象
22 类限制
利开发XYZ框架面代码配置构件通常需开发户界面：（a）行动ActionForm类xml条目（b）服务接口实现类（C）DAO接口实现类（d）间赖关系理开始开发例必须意识类赖需
23 测试技术
测试应该发展程中组成部分开发XYZ框架构建应程序单元测试测试方法服务集成层表现层构件（动作类）采取单元测试测试目确保行类封装工程预期测试时组件整合应程序单元测试开发XYZ框架开发基JUnit框架单元测试集成测试需代码赖关系试验目确保阶层间整合（开发商开发）工作原理功测试程中重点通数描述情况应程序功测试功测试通常需测试类中服务层数户接口层测试真正赖关系进行
执行类型测试开发应程序必须检验列出测试应程序基特征（1）开发单元测试集成测试缓解应该必数源够单元测试队列时应该够模拟赖关系测试代码（2）模拟功测试种测试场景轻松（3）重新运行测试反复应生命周期缓解（4）清洁测试代码分离应程序代码
结构良应程序设计问题介绍服务数访问设计测试应程序非常重应吸气剂开始编码者变量等然结合提供需解决方案单元测试测试方法基构建块开发框架设计利XYZ测试应程序开发：提供测试模板类创建单元测试适应试验应易配置需单元测试运行JUnit测试专门开发默认创建脚提供务运行单元测试务称生成部署EAR文件单独运行
24 Web演示文稿设计
开发XYZ框架Struts框架概念JavaScript实现表示关注提供额外功延长项目Struts框架进行开发首先建立动作servletwebxml然建立配置动作映射形成豆方strutsconfigxml前建立验证规xml
种方法已XYZ框架创建应程序改变开发商直接编辑strutsconfigxmlxml指定信息xdoclet注释ActionForm类直接行动然信息通运行Ant脚转移strutsconfigxmlxml
两种类型验证必需：格式数验证业务逻辑验证数格式验证表现层业务逻辑验证时服务层做业务逻辑验证错误服务层中发生应该定义异常处理
表现层设计目标：（1）动作级提升JSP程序单网页必须单动作类处理（2）赖xdoclet注释指定验证规（3）开发商应避免量减少Session象阻碍扩展性
XYZ框架提供默认模板动作类包含解决述设计目标层面典型代码开发网页求：（1）创建新JSP默认隐藏字段actiontype预计页面出现户行处理（2）创建新动作类扩展类模板作必须指定赖ActionForm具体方法处理户操作表示值隐藏字段actiontype宣布权限访问动作类Spring配置文件（3）创建新ActionForm类指定验证规xdoclet注释求
旦JSPActionActionForm创建必运行Ant脚生成Struts配置XML文件
25 数库访问
发达XYZ框架支持直接JDBCHibernate框架坚持发送数关系数库构建应程序应程序配置必Spring文文件道直接JDBC必须Spring框架jdbcdaosupportjava类扩展样Hibernate DAO必须Spring框架hibernatedaosupportjava类扩展
26 通注释配置
开发XYZ框架Spring框架保持应程序间赖关系代码赖关系（例ActionActionForm间）配置Struts配置XML（例服务道间）配置Spring应程序文文件（XML ApplicationContext）团队环境配置文件开发商什版突配置文件会发生开发XYZ框架提供新效方法特殊注解指定赖关系通注释结构变简单突更改配置避免工件
3 开发框架服务
开发XYZ框架促进普通Java象（POJO）实现业务逻辑业务逻辑必须声明接口服务实现必须实现业务接口建议服务层定义业务异常时业务规验证错误开发XYZ框架采种基Spring框架声明式事务理办法面方面编程（AOP）实现
开发XYZ框架促进良分离部署接口实践（服务消费者合）服务接口（合代表应程序业务逻辑）配置接口Java接口表示WSDL服务暴露实现该接口类必须委托请求实现服务接口类保证业务逻辑保持正确层方服务接口Java接口代表业务逻辑数情况部署接口包含服务接口方法子集
Apache Axis 124 Web服务框架Web服务目前标准Web服务开发两种方法合合间差异首先方法先创建WSDL否代码生成
合第方法开发Web服务做法服务消费者提供者外部供应商技术实现Web服务（代Java）
4 中间层集成
结合外部资源数库Web服务种技术开发XYZ框架技术逻辑层称集成层层设计目标：（1）数库访问采JDBCHibernate应该封装数访问象（DAO）（2）消费Web服务应该简单（3）外部数格式转换成应程序域象应限层（4）层单元测试类应该简单容易事
开发XYZ框架支持HibernateJDBC调访问关系数库推荐SpringJdbcTemplate模板类模板类直接JDBC访问关系型数库建议应DAOSpring框架jdbcdaosupport延伸JdbcTemplate类理数库访问资源（例PreparedStatement）开发XYZ框架插入数源应程序配置文件道Hibernate访问关系数库HibernateSessionFactory通应程序配置文件注入应DAO
5 开发生命周期
开发XYZ框架强调结构够开发团队角色相互关系明确定义三角色描述种角色间相互作应开发成功完成关键（）前端开发员专注开发JSP行动ActionForm类web服务（b）服务开发者专注开发应服务整合服务应程序部分（C）集成开发员致力开发集成构件道Web服务
发展中基问题开发集成代码时赖组件没准备开发XYZ框架解决问题声明方式注入模仿象取代真正象作开发生命周期进展模拟象提供结构配置设置应程序配置力该框架够测试团队发展程中组成部分通编写运行JUnit测试成该框架重点测试应服务赖关系应程序部署单企业档（EAR）文件发达Ant脚生成EAR文件手动运行定期通调度器建议创建部署耳朵运行JUnit测试
6 结
文中作者提供开发J2EE框架概述作者已解决重构架技术发展步骤应该J2EE项目中考虑信息现实世界验旨帮助开发员构建J2EE系统设计定义框架然仅仅冰山角没短文详细描述J2EE潜科学企业应程序影响特基非线性分析仿真软件网
Defining methodologies for developing J2EE webbased information systems
Volume 71 Issue 12 15 December 2010 Pages e1633–e1637
Askar S Boranbayev
EurasianNationalUniversity5MunaitpassovStreetAstana010008Kazakhstan
Available online 5 February 2010
Abstract
This paper describes the concepts behind the developed framework for Javabased projects and describes how it can be used for IT projects The developed framework was created because many common design and development tasks are being repeated in different ways and are not always consistent with best practices We have identified common application concerns and delivered design patterns and tools that represent effective solutions The developed framework delivers (1) an application development stack starting from the user interface to data integration (2) an architecture infrastructure and associated techniques for enhancing and leveraging some other frameworks The proposed architecture defines a development methodology which is designed to assist in custom development projects
Keywords
J2EE
Framework
Web development
1 Introduction
Software tools and packages for the nonlinear analysis of complex spatial–dynamic systems increasingly use Webbased networking platforms for the implementation of their user interface scientific analysis distribution of simulation results and information exchange among scientists The realtime Webbased access to nonlinear analysis simulation software becomes a critical part of many applied systems The intensive technological change in networking hardware and software [1] provides more freedom of choices than in the past [2] Therefore the rational selection and development of the Web platform is of increasing importance for the whole area of nonlinear analysis and its numerous applications The current stage of Web development is characterized by the emergence of a significant number of open source frameworks Frameworks shift the focus of Web development to a higher level allowing the reuse of basic functionality and thus increasing the productivity of development
In some cases open source frameworks do not provide a solution to common problems For this reason developers build their own development framework on top of an open source framework The aim of this paper is to describe a developed Javabased framework that leverages open source frameworks and assists in developing Webbased applications By analyzing some existing open source frameworks this paper presents a new architecture infrastructure and associated techniques for enhancing and leveraging some other frameworks The proposed architecture defines its own development methodology which is designed to assist in custom development projects and integration projects
There are common application design concerns which are often used across projects Even across unique functional requirements there are commonly occurring patterns of use cases which lend themselves to design and development reuse This paper describes a customized framework which had been developed in an effort to identify such common application concerns and identify design patterns that can be used by the developers This framework which we will refer to as the developed XYZ framework provides a set of patterns and tools that were built on industry best practices tailored to common application concerns It provides an application development stack from presentation to integration layers This paper articulates these application concerns and the patterns tools and industry best practices The developed XYZ framework can be customized to various projects’ needs It was developed and configured based on various frameworks and tools such as Struts Spring Hibernate and JUnit
2 Major technologies of the developed framework
21 Layers and separation of code and configuration
Web applications have various design concerns such as presentation business logic data access and security A separation of design concerns into distinct code layers has several advantages such as ease of maintenance the ability to implement good design patterns and the ability to select specialized tools and techniques for specific concerns Separating a project into layers can result in dependencies between those layers For example a singleuse case involving simple data entry and inquiry usually must integrate presentation business logic and data access together to deliver required functionality [3] Therefore there must be a well defined strategy to manage the dependency relationships The developed XYZ framework combines design patterns reusable code and configuration files to make this as easy as possible This framework uses Spring’s Inversion of Control to manage dependencies The Spring Framework [4] provides a way to tie together the objects that make up an application It accomplishes this goal with the Spring Application Context which is a strategy for managing dependencies between objects Spring uses dependency injection and method interception techniques described below
The code that we write is dependent on the objects it uses It is responsible for creating these objects This may result in tight coupling but we would prefer that our code be loosely coupled Dependency injection is a technique which helps us to accomplish this Dependency injection is a form of Inversion of Control (IoC) [5] When applications use dependency injection the code becomes much cleaner and easier to follow It is also loosely coupled allowing for easier configuration and testing The XYZ framework uses several Spring application context files to define dependencies between the layers Method interception is a concept of Aspect Oriented Programming (AOP) [6] Spring AOP implements method interception through JDK dynamic proxies The XYZ framework uses Spring AOP to manage concerns such as transaction management and performance monitoring
The developed XYZ framework consists of two distinct parts code and configuration Code resides in a particular application layer and focuses on a particular piece of the application solution This could be interacting with a database or presenting data to the screen Configuration glues the various layers of the application together Separating configuration from code allows us to manage configuration independently giving us the flexibility of applying different configurations to the same code base For example a Data Access Objects (DAO) implementation knows that it is using JDBC to connect to a database through a data source but it does not know anything about the implementation of that data source It may come from a Java Naming and Directory Interface (JNDI) context or be derived from a driver manager It may point to the remote database or a local database Regardless of where the data source comes from the DAO implementation will operate on the data source in the same manner Likewise a Service object may depend on a DAO but it does not know whether the DAO is implemented via Hibernate straight JDBC or a Web service The service object interacts with the DAO in the same manner regardless of the DAO’s implementation
Spring gives us a way to manage our application’s entire configuration through a Spring application context defined by a set of XML files We could define the application context in one file However by defining it in groups of smaller files we can simplify configuration management A logical set of such application context files which forms a complete application configuration is called a configuration set
During the development of Javabased enterprise applications the standard configuration is where a framework’s configuration set uses external resources such as data sources and JNDI resources This type of configuration sometimes can create problems with (1) An incomplete database that has not yet been loaded Developers may want to test the display of certain types of data but if the underlying database has not yet been completed they will not be able to do this (2) Services or DAOs that may not have been developed yet Integrating with unfinished services or DAOs may halt development
These issues decrease productivity The developed XYZ framework has separated its configuration from its code we can use an alternate configuration set targeted specifically towards development This relieves us from worrying about the availability of external systems which are irrelevant to solving immediate development needs
The developed XYZ framework defines two configuration sets default and standalone We can also customize our application by adding additional configuration sets based on our project needs The default configuration set connects to the development database using the DataSource defined in JNDI It uses fully developed application services and DAOs The standalone configuration set is the most flexible environment for development This configuration set (1) connects to either a locally installed database or the development database using a DriverManagerDataSource (2) uses Spring’s DataSourceTransactionManager for local transaction management (3) uses fully developed application Services and DAOs and (4) fully wired Spring application contexts can be run and tested entirely outside of the application server
The developed XYZ framework is configured by its application context The application context may be defined in one or more XML files A configuration set is a set of XML files that define one application context The configuration set consists of two parts service and Web The service part defines services DAOs and resources for the service and integration layers The Web part defines components for the presentation layer A configuration set cannot be complete without both of these parts
The developed XYZ framework configuration sets are grouped together by what Spring calls a bean reference context defined in the files beanRefContextxml and applicationContextMappingproperties The beanRefContextxml file defines the service part of all configuration sets This file is located in the srcconfig directory of the service project Application context files shared between configuration sets are also located in this directory In addition each configuration set has its own subdirectory which contains files specific to it Services and DAOs for instance are shared between configuration sets while supporting services (like data sources) belong in the subdirectories XML files define the Spring beans in this application by using the 〈bean〉 tag A Spring bean is a Java object created and initialized by the application context
22 Classes and dependencies
Using the developed XYZ framework the following code and configuration artifacts will be typically required to develop a user interface screen (a) Action ActionForm classes and validationxml entries (b) service interface and implementation class (c) DAO interface and implementation class (d) dependency management between all of the above When starting development for a use case we must be aware of the need of all these classes and their dependencies upfront
23 Testing technology
Testing should be an integral part of the development process For applications built using the developed XYZ framework unit testing means testing methods of a single class in the service or integration layer Presentation layer artifacts (Action classes) are not taken up for unit testing The purpose of this test is to ensure that the behavior encapsulated by the class works as expected when testing integration with other components Unit tests in applications developed using the developed XYZ framework are based on the JUnit framework [7] Unlike unit tests integration tests do require code dependencies to be available The purpose of this test is to ensure that the integration between different classes (developed by different developers) works as expected During the Functional Testing process the focus is on testing functionality of the application by using data to depict different scenarios Functional testing typically involves testing classes in the Service layer with different data It can also be performed by testing the user interface layer and by using real dependencies
In order to perform different types of testing the application being developed must be testable Let us list some of the basic characteristics of a testable application (1) Ease of developing unit and integration tests We should be able to unit test without necessarily using data sources or queues Also we should be able to mock dependencies of code under test (2) Ease of simulating various test scenarios for functional testing (3) Ease of rerunning all tests repeatedly over the life cycle of the application (4) Clean separation of testing code from application code
A well structured application that separates design concerns such as presentation services and data access is important for designing testable applications Application coding starts with getters setters variables etc which are then integrated to provide the required solution Unit tests are a fundamental building block for any testing approach The developed XYZ framework’s design facilitates development of testable applications by providing testing template classes that help to create unit tests and also by enabling easy configuration of application to adapt to testing needs Unit tests can be run like any JUnit test The specially developed default build script provides a task to run unit tests This task can be called when generating an EAR file for deployment or can be run separately
24 Web presentation design
The developed XYZ framework uses the Struts framework concepts and JavaScript to implement presentation concerns and provides additional features that can be extended for use in projects When using the Struts framework for development at first we set up the Action Servlet in webxml then we set up configuration action mappings form beans and local forwards in the strutsconfigxml and finally we set up validation rules in validationxml
This approach has been changed in applications that were built using the developed XYZ framework such that developers must not directly edit the strutsconfigxml or validationxml Instead we specify this information as XDoclet annotations in the Action and ActionForm classes directly This information is then transferred into the strutsconfigxml and validationxml by running the Ant script
There are two types of validations that are required data format validation and business logic validation Data format validations are best done in the presentation layer while business logic validations are best done in the services layer Business logic validation errors which occur in the service layer should be handled by throwing custom exceptions
The following are design goals for the presentation layer (1) There is only one Action class ascending one ActionForm per JSP A single Web page must all be handled in a single Action class (2) Dependencies and validation rules are specified using XDoclet annotations (3) Developers should avoid or minimize the use of session objects because it hinders scalability
The XYZ framework provides a default template Action class that contains a solution to the above mentioned design goals for this layer The following are typical code artifacts required for developing a Web page (1) Create a new JSP with a default hidden field called actionType for use in handling user actions that are expected to occur on the page (2) Create a new Action class that extends this template Action class We must specify dependencies on ActionForm specific methods that handle user actions represented by values in hidden field actionType After that we can declare permissions that are required in order to access this Action class This is done in the Spring configuration files (3) Create a new ActionForm class and specify validation rules as required using XDoclet annotations
Once the JSP Action and ActionForm are created it is necessary to run the Ant script to regenerate the strutsconfigxml file
25 Database access
Applications built with the developed XYZ framework support the use of direct JDBC and Hibernate framework to persist in sending data to relational databases The application is configured with the necessary Spring context files DAOs that use direct JDBC must extend from Spring framework’s JdbcDaoSupportjava class Similarly DAOs that use Hibernate must extend from Spring framework’s HibernateDaoSupportjava class
26 Configuration through annotation
The developed XYZ framework uses the Spring framework to maintain dependencies between code artifacts in applications Some of these dependencies (eg between Action and ActionForm) are configured in strutsconfigxml while some others (eg between Service and DAO) are configured in Spring application context files (applicationContextxml) In a team environment these configuration files are shared by developers That is why version conflicts on these configuration files might occur The developed XYZ framework provides a new efficient approach that uses special annotations to specify all of these dependencies By using these annotations configurations become simpler and conflicting changes to configuration artifacts are avoided
3 Services of the developed framework
The developed XYZ framework promotes the use of PlainOldJavaObjects (POJOs) to implement business logic Business logic must be declared as interfaces All service implementations must implement one or more business interfaces It is recommended that the service layer throws custom business exceptions when there are business rule validation errors The developed XYZ framework adopts a declarative transaction management approach based on the Spring framework [8] This is implemented using Aspect Oriented Programming (AOP)
The developed XYZ framework promotes a good practice of separating the deployment interface (contract with service consumers) from the service interface (contract representing application business logic) Deployment interface is a Java interface that represents the service exposed in the WSDL The class that implements this interface always must delegate requests to the class that implements the service interface This ensures that all business logic is maintained at one place in the correct layer Service interface is a Java interface that represents business logic In most cases the deployment interface will contain a subset of methods from the service interface
Apache Axis 124 Web service framework is the current standard for Web services When developing Web services there are two distinct approaches [9] contract first and contract last The difference between contract first and contract last approaches lies in whether the WSDL is created first or whether it is generated from code
Contract first approach is a good practice for developing Web services when the service consumer and provider are external vendors who might implement the Web service using different technologies from each other (they may useNET instead of Java) [10]
4 Middle layer integration
There are several techniques for integrating with the external resources such as databases and Web service The developed XYZ framework uses these techniques in a logical layer called the integration’ layer The design goals for this layer are (1) Access to databases using JDBC or Hibernate should be encapsulated in Data Access Objects (DAO) (2) Consuming Web services should be as simple as possible (3) All conversion of external data formats into application domain objects should be restricted to this layer (4) Unit testing classes in this layer should be simple and easy to do
The developed XYZ framework supports the use of Hibernate and direct JDBC calls to access relational databases It is recommended to use Spring framework’s template classes JdbcTemplate and HibernateTemplate When using direct JDBC to access relational databases it is recommended that the application’s DAOs extend from Spring framework’s JdbcDaoSupport The JdbcTemplate class manages resources used in accessing databases (for example PreparedStatement) The developed XYZ framework inserts the data source into DAOs using application configuration files When using Hibernate to access relational databases the Hibernate SessionFactory is injected into the application DAOs through application configuration files
5 Development life cycle
The developed XYZ framework’s emphasis on structure enables clear definition of roles and their interactions in a development team Three roles are described below An interaction between such roles is critical to the successful completion of application development (a) Front end developers are focused on developing JSPs ActionActionForm classes and exposing Web services (b) Services developers are focused on developing application services and integrating the different parts of the application used by these services (c) Integration developers are focused on developing integration artifacts such as DAOs or consuming Web services
One of the basic problems in development is how to develop and integrate code when its dependent components are not ready or available The developed XYZ framework resolves this problem by providing a structure to declaratively inject mock objects and also replace mock objects with real objects as the development life cycle progresses This is possible due to the ability to configure our application using different configuration sets The framework enables teams to make testing an integral part of the development process This is made possible by writing and running JUnit tests The framework is focused on testing application services and their dependencies Applications are deployed in a single Enterprise Archive (EAR) file The developed Ant script generates this EAR file and can be run manually or periodically through a scheduler It is recommended to run all the JUnit tests before creating the EAR for deployment
6 Conclusion
In this paper the author has provided an overview of the developed J2EE framework The author has addressed important architecture topics technologies and development steps that one should consider in a J2EE project The information is taken from realworld experiences and is intended to help developers build J2EE systems and design their own custom frameworks This however is just the tip of the iceberg as no short paper could describe in detail J2EE’s potential impact on scientific and enterprise applications and especially on Webbased simulation software for nonlinear analysis
Acknowledgements
The author is grateful to his PhD advisor Professor Yuri Yatsenko (from Houston Baptist University) for his advice
References
[1] N Hritonenko Yu Yatsenko
Creative destruction of computing systems Analysis and modeling
Journal of Supercomputing 38 (2006) pp 143–154
[2] Yu Yatsenko N Hritonenko
Network economics and optimal replacement of agestructured IT capital
Mathematical Methods of Operations Research 65 (2007) pp 483–497
[3] AS Boranbayev
Reference architecture for web applications
Reports of the National Academy of Science of the Republic of Kazakhstan 5 (2007) pp 18–26
[4] The Spring Framework official website
[5] Martin Fowler discusses details of the dependency injection pattern and how spring injects dependencies
[6] Spring reference manual’s chapter on aspect oriented programming with spring
[7] JUnit framework
[8] Spring Framework official website Chapter 9 Transaction management
[9] AS Boranbayev
Optimal methods for java web services
News of the National Academy of Science of the Republic of Kazakhstan 5 (2007) pp 38–43
[10] Spring Framework official website Chapter 2
（正文页面够加页正文附外文原文统A4纸张印手工誊写）
文档香网(httpswwwxiangdangnet)户传
《香当网》用户分享的内容，不代表《香当网》观点或立场，请自行判断内容的真实性和可靠性！
该内容是文档的文本内容，更好的格式请下载文档
学生毕业设计（文）外文译文
学生姓名：
学号：
专业名称：电子商务
译文标题（中英文）：定义开发J2EE Web信息系统方法（Defining methodologies for developing J2EE webbased information systems）
译文出处：Elsevier ScienceDirect全文期刊数库
指导教师审阅签名：
外文译文正文：
摘：
文介绍基Java开发项目框架概念背景介绍开发IT项目开发框架产生许设计开发工作正方式重复总佳实践相致已确定企业交付应设计模式工具效解决方案现开发框架提供：（1）应开发堆栈户界面数整合（2）提高利框架基础设施相关技术体系结构该体系结构定义开发方法目协助户开发项目
1 介绍
软件工具复杂空间系统分析越越应Web户界面实现基网络台科学分析模拟结果分布科学家间信息交换实时基Web访问非线性分析模拟软件成许应系统关键部分强化技术改变网络硬件软件提供更选择WEB台合理选择发展非线性分析整区日益增加重性众应网站目前发展阶段特点量开源框架出现框架式Web开发重点转移更高水基功重提高开发效率
某情况开源框架没提供解决常见问题方法开发商建立开发框架顶部开源框架文目描述基Java开发框架利开源框架协助开发基Web应程序通现开源框架文提出种新体系结构提高利框架基础设施相关技术该架构定义开发方法目协助项目定制开发集成项目
常见应设计问题项目独特功求常模式情况身设计开发利文介绍种定制框架直努力寻找样常见应问题确定设计模式开发商开发框架称发达XYZ框架提供套模式工具建立行业佳实践针常见应问题提供应开发堆栈表现集成层文阐述应问题模式工具行业佳实践开发框架定制XYZ种工程需开发配置基框架工具StrutsSpringHibernateJUnit
2 开发框架技术
21 代码层配置分离
Web应程序设计问题介绍业务逻辑数访问安全分离设计问题分代码层具优点：易维护实现良设计模式力够选择专门工具技术具体问题分离成项目层导致层间赖关系例案例涉简单数录入查询通常必须整合显示业务逻辑数访问起提供需功必须良定义策略理赖关系XYZ框架相结合开发设计模式重代码配置文件容易该框架采控制弹簧反转理赖性Spring框架[提供种方式联系起构成应程序象实现目标Spring应程序文理象间赖关系策略Spring赖注入方法拦截技术介绍
写代码赖象负责创建象会导致紧耦合希代码松散耦合赖注入种技术帮助完成赖注入种形式控制反转（IoC）应程序赖注入代码变更干净更容易理解松散耦合允许更容易配置测试XYZ框架采Spring应文文件定义层层间赖关系方法拦截面方面编程（AOP）概念通JDK动态代理Spring AOP实现方法拦截XYZ框架Spring AOP理等问题事务理性监测
开发XYZ框架两部分组成：代码配置代码驻留特定应层集中特定应解决方案数库交互提交数屏幕结构胶种应层代码分离配置允许独立理结构配置相代码库灵活性例数访问象（DAO）实现知道通数源JDBC连接数库知道数源执行什Java命名目录接口（JNDI）文驱动程序理器指远程数库数库数源里道实施数源操作方式样服务象赖道知道刀通HibernateJDBC实现直Web服务服务象相方式道相互作DAO实现
Spring提供种通Spring应文理应程序整结构组XML文件定义文件中定义应程序文然较文件组中定义简化配置理样应程序文文件形成完整应程序配置逻辑集合称配置集
开发基Java企业应程序标准配置框架配置设置外部资源数源JNDI资源种类型配置时产生问题：（1）完整数库尚未加载开发商想测试某类型数显示果基础数库尚未完成够样做（2）服务道没开发出结合未完成服务DAO停止发展
问题降低生产效率开发XYZ框架已代码分离结构配置设置专门针发展减轻担心外部系统性解决眼前发展关需求
开发XYZ框架定义两配置设置：默认独立定义应程序添加基项目需额外配置集默认配置设置连接定义JNDI DataSource开发数库充分开发应服务道独立配置集发展灵活环境配置集：（1）连接安装数库DriverManagerDataSource开发数库（2）弹簧方DataSourceTransactionManager事务理（3）充分利开发应服务道（4）完全线Spring应程序文运行测试完全应服务器外面
开发框架XYZ应文配置应程序文XML文件中定义配置集组XML文件定义应程序文配置集分两部分：服务Web服务部分定义服务DAO资源服务整合层Web部件定义表示层组件配置集没两部分完整
开发XYZ框架配置集调bean引文件定义分组applicationcontextmappingproperties beanrefcontextxmlbeanrefcontextxml文件定义配置服务集文件位服务项目src 配置目录配置设置应程序文间享文件位目录外配置子目录中包含特定文件例服务道间配置设置享时支持服务（数源）属子目录XML文件定义弹簧豆应中MathML查源〈bean〉标签Spring bean创建应程序文初始化Java象
22 类限制
利开发XYZ框架面代码配置构件通常需开发户界面：（a）行动ActionForm类xml条目（b）服务接口实现类（C）DAO接口实现类（d）间赖关系理开始开发例必须意识类赖需
23 测试技术
测试应该发展程中组成部分开发XYZ框架构建应程序单元测试测试方法服务集成层表现层构件（动作类）采取单元测试测试目确保行类封装工程预期测试时组件整合应程序单元测试开发XYZ框架开发基JUnit框架单元测试集成测试需代码赖关系试验目确保阶层间整合（开发商开发）工作原理功测试程中重点通数描述情况应程序功测试功测试通常需测试类中服务层数户接口层测试真正赖关系进行
执行类型测试开发应程序必须检验列出测试应程序基特征（1）开发单元测试集成测试缓解应该必数源够单元测试队列时应该够模拟赖关系测试代码（2）模拟功测试种测试场景轻松（3）重新运行测试反复应生命周期缓解（4）清洁测试代码分离应程序代码
结构良应程序设计问题介绍服务数访问设计测试应程序非常重应吸气剂开始编码者变量等然结合提供需解决方案单元测试测试方法基构建块开发框架设计利XYZ测试应程序开发：提供测试模板类创建单元测试适应试验应易配置需单元测试运行JUnit测试专门开发默认创建脚提供务运行单元测试务称生成部署EAR文件单独运行
24 Web演示文稿设计
开发XYZ框架Struts框架概念JavaScript实现表示关注提供额外功延长项目Struts框架进行开发首先建立动作servletwebxml然建立配置动作映射形成豆方strutsconfigxml前建立验证规xml
种方法已XYZ框架创建应程序改变开发商直接编辑strutsconfigxmlxml指定信息xdoclet注释ActionForm类直接行动然信息通运行Ant脚转移strutsconfigxmlxml
两种类型验证必需：格式数验证业务逻辑验证数格式验证表现层业务逻辑验证时服务层做业务逻辑验证错误服务层中发生应该定义异常处理
表现层设计目标：（1）动作级提升JSP程序单网页必须单动作类处理（2）赖xdoclet注释指定验证规（3）开发商应避免量减少Session象阻碍扩展性
XYZ框架提供默认模板动作类包含解决述设计目标层面典型代码开发网页求：（1）创建新JSP默认隐藏字段actiontype预计页面出现户行处理（2）创建新动作类扩展类模板作必须指定赖ActionForm具体方法处理户操作表示值隐藏字段actiontype宣布权限访问动作类Spring配置文件（3）创建新ActionForm类指定验证规xdoclet注释求
旦JSPActionActionForm创建必运行Ant脚生成Struts配置XML文件
25 数库访问
发达XYZ框架支持直接JDBCHibernate框架坚持发送数关系数库构建应程序应程序配置必Spring文文件道直接JDBC必须Spring框架jdbcdaosupportjava类扩展样Hibernate DAO必须Spring框架hibernatedaosupportjava类扩展
26 通注释配置
开发XYZ框架Spring框架保持应程序间赖关系代码赖关系（例ActionActionForm间）配置Struts配置XML（例服务道间）配置Spring应程序文文件（XML ApplicationContext）团队环境配置文件开发商什版突配置文件会发生开发XYZ框架提供新效方法特殊注解指定赖关系通注释结构变简单突更改配置避免工件
3 开发框架服务
开发XYZ框架促进普通Java象（POJO）实现业务逻辑业务逻辑必须声明接口服务实现必须实现业务接口建议服务层定义业务异常时业务规验证错误开发XYZ框架采种基Spring框架声明式事务理办法面方面编程（AOP）实现
开发XYZ框架促进良分离部署接口实践（服务消费者合）服务接口（合代表应程序业务逻辑）配置接口Java接口表示WSDL服务暴露实现该接口类必须委托请求实现服务接口类保证业务逻辑保持正确层方服务接口Java接口代表业务逻辑数情况部署接口包含服务接口方法子集
Apache Axis 124 Web服务框架Web服务目前标准Web服务开发两种方法合合间差异首先方法先创建WSDL否代码生成
合第方法开发Web服务做法服务消费者提供者外部供应商技术实现Web服务（代Java）
4 中间层集成
结合外部资源数库Web服务种技术开发XYZ框架技术逻辑层称集成层层设计目标：（1）数库访问采JDBCHibernate应该封装数访问象（DAO）（2）消费Web服务应该简单（3）外部数格式转换成应程序域象应限层（4）层单元测试类应该简单容易事
开发XYZ框架支持HibernateJDBC调访问关系数库推荐SpringJdbcTemplate模板类模板类直接JDBC访问关系型数库建议应DAOSpring框架jdbcdaosupport延伸JdbcTemplate类理数库访问资源（例PreparedStatement）开发XYZ框架插入数源应程序配置文件道Hibernate访问关系数库HibernateSessionFactory通应程序配置文件注入应DAO
5 开发生命周期
开发XYZ框架强调结构够开发团队角色相互关系明确定义三角色描述种角色间相互作应开发成功完成关键（）前端开发员专注开发JSP行动ActionForm类web服务（b）服务开发者专注开发应服务整合服务应程序部分（C）集成开发员致力开发集成构件道Web服务
发展中基问题开发集成代码时赖组件没准备开发XYZ框架解决问题声明方式注入模仿象取代真正象作开发生命周期进展模拟象提供结构配置设置应程序配置力该框架够测试团队发展程中组成部分通编写运行JUnit测试成该框架重点测试应服务赖关系应程序部署单企业档（EAR）文件发达Ant脚生成EAR文件手动运行定期通调度器建议创建部署耳朵运行JUnit测试
6 结
文中作者提供开发J2EE框架概述作者已解决重构架技术发展步骤应该J2EE项目中考虑信息现实世界验旨帮助开发员构建J2EE系统设计定义框架然仅仅冰山角没短文详细描述J2EE潜科学企业应程序影响特基非线性分析仿真软件网
Defining methodologies for developing J2EE webbased information systems
Volume 71 Issue 12 15 December 2010 Pages e1633–e1637
Askar S Boranbayev
EurasianNationalUniversity5MunaitpassovStreetAstana010008Kazakhstan
Available online 5 February 2010
Abstract
This paper describes the concepts behind the developed framework for Javabased projects and describes how it can be used for IT projects The developed framework was created because many common design and development tasks are being repeated in different ways and are not always consistent with best practices We have identified common application concerns and delivered design patterns and tools that represent effective solutions The developed framework delivers (1) an application development stack starting from the user interface to data integration (2) an architecture infrastructure and associated techniques for enhancing and leveraging some other frameworks The proposed architecture defines a development methodology which is designed to assist in custom development projects
Keywords
J2EE
Framework
Web development
1 Introduction
Software tools and packages for the nonlinear analysis of complex spatial–dynamic systems increasingly use Webbased networking platforms for the implementation of their user interface scientific analysis distribution of simulation results and information exchange among scientists The realtime Webbased access to nonlinear analysis simulation software becomes a critical part of many applied systems The intensive technological change in networking hardware and software [1] provides more freedom of choices than in the past [2] Therefore the rational selection and development of the Web platform is of increasing importance for the whole area of nonlinear analysis and its numerous applications The current stage of Web development is characterized by the emergence of a significant number of open source frameworks Frameworks shift the focus of Web development to a higher level allowing the reuse of basic functionality and thus increasing the productivity of development
In some cases open source frameworks do not provide a solution to common problems For this reason developers build their own development framework on top of an open source framework The aim of this paper is to describe a developed Javabased framework that leverages open source frameworks and assists in developing Webbased applications By analyzing some existing open source frameworks this paper presents a new architecture infrastructure and associated techniques for enhancing and leveraging some other frameworks The proposed architecture defines its own development methodology which is designed to assist in custom development projects and integration projects
There are common application design concerns which are often used across projects Even across unique functional requirements there are commonly occurring patterns of use cases which lend themselves to design and development reuse This paper describes a customized framework which had been developed in an effort to identify such common application concerns and identify design patterns that can be used by the developers This framework which we will refer to as the developed XYZ framework provides a set of patterns and tools that were built on industry best practices tailored to common application concerns It provides an application development stack from presentation to integration layers This paper articulates these application concerns and the patterns tools and industry best practices The developed XYZ framework can be customized to various projects’ needs It was developed and configured based on various frameworks and tools such as Struts Spring Hibernate and JUnit
2 Major technologies of the developed framework
21 Layers and separation of code and configuration
Web applications have various design concerns such as presentation business logic data access and security A separation of design concerns into distinct code layers has several advantages such as ease of maintenance the ability to implement good design patterns and the ability to select specialized tools and techniques for specific concerns Separating a project into layers can result in dependencies between those layers For example a singleuse case involving simple data entry and inquiry usually must integrate presentation business logic and data access together to deliver required functionality [3] Therefore there must be a well defined strategy to manage the dependency relationships The developed XYZ framework combines design patterns reusable code and configuration files to make this as easy as possible This framework uses Spring’s Inversion of Control to manage dependencies The Spring Framework [4] provides a way to tie together the objects that make up an application It accomplishes this goal with the Spring Application Context which is a strategy for managing dependencies between objects Spring uses dependency injection and method interception techniques described below
The code that we write is dependent on the objects it uses It is responsible for creating these objects This may result in tight coupling but we would prefer that our code be loosely coupled Dependency injection is a technique which helps us to accomplish this Dependency injection is a form of Inversion of Control (IoC) [5] When applications use dependency injection the code becomes much cleaner and easier to follow It is also loosely coupled allowing for easier configuration and testing The XYZ framework uses several Spring application context files to define dependencies between the layers Method interception is a concept of Aspect Oriented Programming (AOP) [6] Spring AOP implements method interception through JDK dynamic proxies The XYZ framework uses Spring AOP to manage concerns such as transaction management and performance monitoring
The developed XYZ framework consists of two distinct parts code and configuration Code resides in a particular application layer and focuses on a particular piece of the application solution This could be interacting with a database or presenting data to the screen Configuration glues the various layers of the application together Separating configuration from code allows us to manage configuration independently giving us the flexibility of applying different configurations to the same code base For example a Data Access Objects (DAO) implementation knows that it is using JDBC to connect to a database through a data source but it does not know anything about the implementation of that data source It may come from a Java Naming and Directory Interface (JNDI) context or be derived from a driver manager It may point to the remote database or a local database Regardless of where the data source comes from the DAO implementation will operate on the data source in the same manner Likewise a Service object may depend on a DAO but it does not know whether the DAO is implemented via Hibernate straight JDBC or a Web service The service object interacts with the DAO in the same manner regardless of the DAO’s implementation
Spring gives us a way to manage our application’s entire configuration through a Spring application context defined by a set of XML files We could define the application context in one file However by defining it in groups of smaller files we can simplify configuration management A logical set of such application context files which forms a complete application configuration is called a configuration set
During the development of Javabased enterprise applications the standard configuration is where a framework’s configuration set uses external resources such as data sources and JNDI resources This type of configuration sometimes can create problems with (1) An incomplete database that has not yet been loaded Developers may want to test the display of certain types of data but if the underlying database has not yet been completed they will not be able to do this (2) Services or DAOs that may not have been developed yet Integrating with unfinished services or DAOs may halt development
These issues decrease productivity The developed XYZ framework has separated its configuration from its code we can use an alternate configuration set targeted specifically towards development This relieves us from worrying about the availability of external systems which are irrelevant to solving immediate development needs
The developed XYZ framework defines two configuration sets default and standalone We can also customize our application by adding additional configuration sets based on our project needs The default configuration set connects to the development database using the DataSource defined in JNDI It uses fully developed application services and DAOs The standalone configuration set is the most flexible environment for development This configuration set (1) connects to either a locally installed database or the development database using a DriverManagerDataSource (2) uses Spring’s DataSourceTransactionManager for local transaction management (3) uses fully developed application Services and DAOs and (4) fully wired Spring application contexts can be run and tested entirely outside of the application server
The developed XYZ framework is configured by its application context The application context may be defined in one or more XML files A configuration set is a set of XML files that define one application context The configuration set consists of two parts service and Web The service part defines services DAOs and resources for the service and integration layers The Web part defines components for the presentation layer A configuration set cannot be complete without both of these parts
The developed XYZ framework configuration sets are grouped together by what Spring calls a bean reference context defined in the files beanRefContextxml and applicationContextMappingproperties The beanRefContextxml file defines the service part of all configuration sets This file is located in the srcconfig directory of the service project Application context files shared between configuration sets are also located in this directory In addition each configuration set has its own subdirectory which contains files specific to it Services and DAOs for instance are shared between configuration sets while supporting services (like data sources) belong in the subdirectories XML files define the Spring beans in this application by using the 〈bean〉 tag A Spring bean is a Java object created and initialized by the application context
22 Classes and dependencies
Using the developed XYZ framework the following code and configuration artifacts will be typically required to develop a user interface screen (a) Action ActionForm classes and validationxml entries (b) service interface and implementation class (c) DAO interface and implementation class (d) dependency management between all of the above When starting development for a use case we must be aware of the need of all these classes and their dependencies upfront
23 Testing technology
Testing should be an integral part of the development process For applications built using the developed XYZ framework unit testing means testing methods of a single class in the service or integration layer Presentation layer artifacts (Action classes) are not taken up for unit testing The purpose of this test is to ensure that the behavior encapsulated by the class works as expected when testing integration with other components Unit tests in applications developed using the developed XYZ framework are based on the JUnit framework [7] Unlike unit tests integration tests do require code dependencies to be available The purpose of this test is to ensure that the integration between different classes (developed by different developers) works as expected During the Functional Testing process the focus is on testing functionality of the application by using data to depict different scenarios Functional testing typically involves testing classes in the Service layer with different data It can also be performed by testing the user interface layer and by using real dependencies
In order to perform different types of testing the application being developed must be testable Let us list some of the basic characteristics of a testable application (1) Ease of developing unit and integration tests We should be able to unit test without necessarily using data sources or queues Also we should be able to mock dependencies of code under test (2) Ease of simulating various test scenarios for functional testing (3) Ease of rerunning all tests repeatedly over the life cycle of the application (4) Clean separation of testing code from application code
A well structured application that separates design concerns such as presentation services and data access is important for designing testable applications Application coding starts with getters setters variables etc which are then integrated to provide the required solution Unit tests are a fundamental building block for any testing approach The developed XYZ framework’s design facilitates development of testable applications by providing testing template classes that help to create unit tests and also by enabling easy configuration of application to adapt to testing needs Unit tests can be run like any JUnit test The specially developed default build script provides a task to run unit tests This task can be called when generating an EAR file for deployment or can be run separately
24 Web presentation design
The developed XYZ framework uses the Struts framework concepts and JavaScript to implement presentation concerns and provides additional features that can be extended for use in projects When using the Struts framework for development at first we set up the Action Servlet in webxml then we set up configuration action mappings form beans and local forwards in the strutsconfigxml and finally we set up validation rules in validationxml
This approach has been changed in applications that were built using the developed XYZ framework such that developers must not directly edit the strutsconfigxml or validationxml Instead we specify this information as XDoclet annotations in the Action and ActionForm classes directly This information is then transferred into the strutsconfigxml and validationxml by running the Ant script
There are two types of validations that are required data format validation and business logic validation Data format validations are best done in the presentation layer while business logic validations are best done in the services layer Business logic validation errors which occur in the service layer should be handled by throwing custom exceptions
The following are design goals for the presentation layer (1) There is only one Action class ascending one ActionForm per JSP A single Web page must all be handled in a single Action class (2) Dependencies and validation rules are specified using XDoclet annotations (3) Developers should avoid or minimize the use of session objects because it hinders scalability
The XYZ framework provides a default template Action class that contains a solution to the above mentioned design goals for this layer The following are typical code artifacts required for developing a Web page (1) Create a new JSP with a default hidden field called actionType for use in handling user actions that are expected to occur on the page (2) Create a new Action class that extends this template Action class We must specify dependencies on ActionForm specific methods that handle user actions represented by values in hidden field actionType After that we can declare permissions that are required in order to access this Action class This is done in the Spring configuration files (3) Create a new ActionForm class and specify validation rules as required using XDoclet annotations
Once the JSP Action and ActionForm are created it is necessary to run the Ant script to regenerate the strutsconfigxml file
25 Database access
Applications built with the developed XYZ framework support the use of direct JDBC and Hibernate framework to persist in sending data to relational databases The application is configured with the necessary Spring context files DAOs that use direct JDBC must extend from Spring framework’s JdbcDaoSupportjava class Similarly DAOs that use Hibernate must extend from Spring framework’s HibernateDaoSupportjava class
26 Configuration through annotation
The developed XYZ framework uses the Spring framework to maintain dependencies between code artifacts in applications Some of these dependencies (eg between Action and ActionForm) are configured in strutsconfigxml while some others (eg between Service and DAO) are configured in Spring application context files (applicationContextxml) In a team environment these configuration files are shared by developers That is why version conflicts on these configuration files might occur The developed XYZ framework provides a new efficient approach that uses special annotations to specify all of these dependencies By using these annotations configurations become simpler and conflicting changes to configuration artifacts are avoided
3 Services of the developed framework
The developed XYZ framework promotes the use of PlainOldJavaObjects (POJOs) to implement business logic Business logic must be declared as interfaces All service implementations must implement one or more business interfaces It is recommended that the service layer throws custom business exceptions when there are business rule validation errors The developed XYZ framework adopts a declarative transaction management approach based on the Spring framework [8] This is implemented using Aspect Oriented Programming (AOP)
The developed XYZ framework promotes a good practice of separating the deployment interface (contract with service consumers) from the service interface (contract representing application business logic) Deployment interface is a Java interface that represents the service exposed in the WSDL The class that implements this interface always must delegate requests to the class that implements the service interface This ensures that all business logic is maintained at one place in the correct layer Service interface is a Java interface that represents business logic In most cases the deployment interface will contain a subset of methods from the service interface
Apache Axis 124 Web service framework is the current standard for Web services When developing Web services there are two distinct approaches [9] contract first and contract last The difference between contract first and contract last approaches lies in whether the WSDL is created first or whether it is generated from code
Contract first approach is a good practice for developing Web services when the service consumer and provider are external vendors who might implement the Web service using different technologies from each other (they may useNET instead of Java) [10]
4 Middle layer integration
There are several techniques for integrating with the external resources such as databases and Web service The developed XYZ framework uses these techniques in a logical layer called the integration’ layer The design goals for this layer are (1) Access to databases using JDBC or Hibernate should be encapsulated in Data Access Objects (DAO) (2) Consuming Web services should be as simple as possible (3) All conversion of external data formats into application domain objects should be restricted to this layer (4) Unit testing classes in this layer should be simple and easy to do
The developed XYZ framework supports the use of Hibernate and direct JDBC calls to access relational databases It is recommended to use Spring framework’s template classes JdbcTemplate and HibernateTemplate When using direct JDBC to access relational databases it is recommended that the application’s DAOs extend from Spring framework’s JdbcDaoSupport The JdbcTemplate class manages resources used in accessing databases (for example PreparedStatement) The developed XYZ framework inserts the data source into DAOs using application configuration files When using Hibernate to access relational databases the Hibernate SessionFactory is injected into the application DAOs through application configuration files
5 Development life cycle
The developed XYZ framework’s emphasis on structure enables clear definition of roles and their interactions in a development team Three roles are described below An interaction between such roles is critical to the successful completion of application development (a) Front end developers are focused on developing JSPs ActionActionForm classes and exposing Web services (b) Services developers are focused on developing application services and integrating the different parts of the application used by these services (c) Integration developers are focused on developing integration artifacts such as DAOs or consuming Web services
One of the basic problems in development is how to develop and integrate code when its dependent components are not ready or available The developed XYZ framework resolves this problem by providing a structure to declaratively inject mock objects and also replace mock objects with real objects as the development life cycle progresses This is possible due to the ability to configure our application using different configuration sets The framework enables teams to make testing an integral part of the development process This is made possible by writing and running JUnit tests The framework is focused on testing application services and their dependencies Applications are deployed in a single Enterprise Archive (EAR) file The developed Ant script generates this EAR file and can be run manually or periodically through a scheduler It is recommended to run all the JUnit tests before creating the EAR for deployment
6 Conclusion
In this paper the author has provided an overview of the developed J2EE framework The author has addressed important architecture topics technologies and development steps that one should consider in a J2EE project The information is taken from realworld experiences and is intended to help developers build J2EE systems and design their own custom frameworks This however is just the tip of the iceberg as no short paper could describe in detail J2EE’s potential impact on scientific and enterprise applications and especially on Webbased simulation software for nonlinear analysis
Acknowledgements
The author is grateful to his PhD advisor Professor Yuri Yatsenko (from Houston Baptist University) for his advice
References
[1] N Hritonenko Yu Yatsenko
Creative destruction of computing systems Analysis and modeling
Journal of Supercomputing 38 (2006) pp 143–154
[2] Yu Yatsenko N Hritonenko
Network economics and optimal replacement of agestructured IT capital
Mathematical Methods of Operations Research 65 (2007) pp 483–497
[3] AS Boranbayev
Reference architecture for web applications
Reports of the National Academy of Science of the Republic of Kazakhstan 5 (2007) pp 18–26
[4] The Spring Framework official website
[5] Martin Fowler discusses details of the dependency injection pattern and how spring injects dependencies
[6] Spring reference manual’s chapter on aspect oriented programming with spring
[7] JUnit framework
[8] Spring Framework official website Chapter 9 Transaction management
[9] AS Boranbayev
Optimal methods for java web services
News of the National Academy of Science of the Republic of Kazakhstan 5 (2007) pp 38–43
[10] Spring Framework official website Chapter 2
（正文页面够加页正文附外文原文统A4纸张印手工誊写）
文档香网(httpswwwxiangdangnet)户传
《香当网》用户分享的内容，不代表《香当网》观点或立场，请自行判断内容的真实性和可靠性！
该内容是文档的文本内容，更好的格式请下载文档
