CN1967485B - A method and system for realizing J2EE application - Google Patents
A method and system for realizing J2EE application Download PDFInfo
- Publication number
- CN1967485B CN1967485B CN200610086757A CN200610086757A CN1967485B CN 1967485 B CN1967485 B CN 1967485B CN 200610086757 A CN200610086757 A CN 200610086757A CN 200610086757 A CN200610086757 A CN 200610086757A CN 1967485 B CN1967485 B CN 1967485B
- Authority
- CN
- China
- Prior art keywords
- business object
- business
- module
- information
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
本发明公开了一种实现J2EE应用的方法和系统，用以解决现有J2EE应用技术中J2EE应用系统的EJB组件设计复杂的问题；该方法由接收到客户端业务请求的EJB客户端模块向业务请求代理模块发送业务请求信息，所述业务请求代理模块由一个标准的EJB组件构成；业务请求代理模块获取业务对象配置信息，并根据该配置信息获取业务对象实例；业务请求代理模块根据所述业务请求信息调用业务对象实例的方法进行业务处理，并将处理结果返回给EJB客户端模块。本发明简化了EJB组件的设计，降低了J2EE系统开发和部署的复杂度。
The invention discloses a method and system for realizing J2EE application, which are used to solve the problem of complex EJB component design of J2EE application system in the existing J2EE application technology; The request agent module sends service request information, and the service request agent module is composed of a standard EJB component; the service request agent module obtains the business object configuration information, and obtains the business object instance according to the configuration information; the service request agent module according to the business request The request information invokes the method of the business object instance for business processing, and returns the processing result to the EJB client module. The invention simplifies the design of EJB components and reduces the complexity of J2EE system development and deployment.
Description
Technical Field
The invention relates to J2EE application technology in the field of communication and computers, in particular to a method and a system for realizing J2EE application.
Background
The J2EE (Java 2Enterprise Edition ) platform is an Enterprise application platform designed for distributed application based on component deployment. As shown in fig. 1, the existing J2EE application system provides background support for each type of component in the form of a container, including a Web container and an EJB (Enterprise application component technology) container; wherein,
the Web container comprises a JSP (Java Server Pages)/Servlet (Java Server end small program) component module and an EJB client module, wherein the JSP/Servlet component module realizes the representation of service logic through JSP or Servlet technology and submits a service request sent by the application client module to the EJB client module; and the EJB client module calls an EJB service logic corresponding to the service request from the EJB container.
And the EJB container is used for storing the EJB service logic realized by the EJB component, is connected with the EJB client module and the database, and is used for specific application service logic and background data persistence.
The J2EE application is generally realized by following a multilayer architecture of a presentation layer, a service logic layer and a data layer, the presentation layer is realized by a JSP/Servlet technology based on a Web container, the JSP/Servlet technology is deployed to an application server according to a Web component format, and the Web container is responsible for responding, scheduling and analyzing and processing service requests; the service logic layer is generally realized based on an EJB component technology of an EJB container, and is deployed to an application server according to the EJB component, and the EJB container provides management of the EJB component in terms of pooling, transaction management, scheduling, clustering, safety and the like.
For large enterprise-level applications, the services are various, and different EJB components are required to implement different service logics. The JSP/Servlet component module receives the application client request, submits the request to the EJB client module in a service object mode after analysis, and the EJB client module calls EJB service logic realized by the corresponding EJB component according to the service request information and returns a service processing result to the application client by the Web container; that is, as long as there is a service request, an EJB service logic corresponding to the service request is needed, and an EJB client caller is also needed to support the calling of the service logic. Therefore, the design and implementation of EJB are complex, different EJB are adopted to implement service logic aiming at different services, the system is large, and the complexity of deployment and maintenance is increased; the service logic adopts a large number of EJB components, and a remote calling design of response needs to be added to the client, so that the complexity of the service application of the client is increased, and the openness is poor; if the remote service logic interface is directly opened to the client, the interface coupling and dependency between the presentation layer and the service logic layer are strengthened.
Disclosure of Invention
The invention provides a method and a system for realizing J2EE application, which are used for solving the problem that the EJB component in a J2EE application system is complex in design due to the use of a large number of EJB components in the prior art.
The invention provides the following technical scheme:
a method of implementing a J2EE application, comprising the steps of:
the EJB client module which receives the client service request sends service request information to a service request proxy module, wherein the service request proxy module consists of an EJB component;
the service request agent module acquires service object configuration information and acquires a service object instance according to the configuration information;
and the service request agent module calls the method of the service object instance to process the service according to the service request information and returns the processing result to the EJB client module.
The step of obtaining the configuration information of the business object comprises the following steps:
the service request agent module analyzes the service request information of the EJB client to obtain a service object type path identifier, a method identifier and parameter information;
the service object information configuration module loads corresponding service object configuration information according to the class path identifier and the method identifier of the service object specified by the service request information, and the information is returned to the service request agent module after being stored in an XML file format or a database format.
The service request information comprises service object type path identification, method identification and parameter information.
The service object configuration information comprises a service object class path name, a method name and transaction attribute information.
And the service request agent module acquires corresponding service object instances from a service object pooling module containing a plurality of service object instances according to the acquired service object configuration information.
The method for obtaining the business object instance also comprises the steps that the business object pooling module judges whether a corresponding business object instance exists, and if the business object instance exists, the business object instance is directly returned to the business request agent module; otherwise, creating a service object instance and transmitting the service object instance to the service request proxy module.
The business object pooling module automatically loads all business object classes during system initialization according to the business object configuration information provided by the business object information configuration module, then initializes the business objects according to the definition of the buffer pool in the business object pooling module, and instantiates the business objects through a Java reflection mechanism.
The business object pooling module stores business object instances according to a buffer pool specification, wherein the buffer pool specification comprises the initialized number and the maximum buffer number of the business objects.
And the service request agent module positions corresponding method objects and transaction attribute information in the service object pooling module according to the obtained service object instances.
Defining a method transaction processing mechanism of a service object as a container management transaction, wherein all service method calls executed by a service request proxy module are guaranteed by the transaction of the container; or defining the method transaction processing mechanism of the service object as a Bean self-management transaction, starting the transaction before calling the method by the service request agent module according to the transaction declaration in the configuration information, and submitting or rolling back the transaction after the method is executed.
A system for implementing a J2EE application, comprising: the Web container is used for responding, scheduling and analyzing the service request, and comprises an EJB client module used for calling EJB service logic corresponding to the service request; the EJB container is used for specific application service logic and background data persistence;
wherein the EJB container includes:
the business object information configuration module is used for configuring the business object and storing the configuration information of the business object;
the business object pooling module is used for providing business object instances and is responsible for data persistence of the business objects;
and the service request proxy module is formed by an EJB component and is used for receiving service request information sent by the EJB client module, acquiring object configuration information from the service object information configuration module, acquiring a service object instance from the service object pooling module according to the configuration information, calling a method of the service object instance to perform service processing and returning a processing result to the EJB client module.
And the service information configuration module loads corresponding service request object configuration information according to the class path identifier and the method identifier specified by the service request information, and the information is stored in an XML file format or a database form.
And the service request agent module positions corresponding method objects and transaction attribute information in the service object pooling module according to the obtained service object instances.
The business object pooling module automatically loads all business object classes during system initialization according to the business object configuration information provided by the business object information configuration module, then initializes the business objects according to the definition of the buffer pool in the business object pooling module, and instantiates the business objects through a Java reflection mechanism.
The business object pooling module stores business object instances according to a buffer pool specification, wherein the buffer pool specification comprises the initialized number and the maximum buffer number of the business objects.
The invention has the following beneficial effects:
1. the service components adopt common POJO (Plain Old Java Objects) type components, so that the quantity of EJB components is reduced, the workload of development, deployment and maintenance of the J2EE system is greatly simplified, and the working efficiency of the system is improved;
2. by adopting a configuration mapping mechanism of a service object, the realization of a presentation layer and a service logic layer in a J2EE application system can be completely separated only by setting a configuration identifier when a client calls a service logic, so that the coupling of the system is reduced;
3. the architecture provides a flexible and customized transaction processing mechanism, and transaction management in the service development process is simplified;
4. the service object adopts a buffer mechanism, so that the service processing capacity of the system is improved.
Drawings
FIG. 1 is a schematic diagram of a prior art J2EE application system;
FIG. 2 is a schematic structural diagram of an application system of J2EE in an embodiment of the present invention;
fig. 3 is a flowchart of service request processing according to an embodiment of the present invention.
Detailed Description
In order to solve the problem that the design of a J2EE application system is complex because a large number of EJB components are used for realizing service logics of different services, the invention uses one EJB component as a proxy to forward information by reducing the number of the EJB components, and adopts common POJO classes to realize the service logics.
As shown in fig. 2, the J2EE application system in this embodiment includes a Web container and an EJB container, where the Web container is used for response, scheduling, and parsing processing of a service request, and includes a JSP/Servlet component module used for implementing representing service logic and submitting a service request object; the EJB client module is used for receiving the service request object information and sending a service request; the EJB container is used for specific application service logic and background data persistence and comprises a service object information configuration module, a service object pooling module and a service request agent module, wherein,
and the service object information configuration module adopts a common JavaBeans component and is used for configuring the service object, storing the configuration information of the service object, and maintaining information such as the class path name, the method name, the transaction declaration of the method and the like of the service object.
And the service object pooling module adopts a common JavaBeans component and is used for providing a service object instance for the service request agent module and is responsible for data persistence of the service object, so that frequent creation and destruction of the service object instance are reduced.
And the service request proxy module adopts a standard EJB component and is used for receiving the service request sent by the EJB client module, acquiring the configuration information from the service object information configuration module, acquiring the corresponding service object example from the service object pooling module according to the configuration information, calling the method of the service object example to perform service processing and returning the processing result to the EJB client module.
As shown in fig. 3, the service request processing procedure in this embodiment is as follows:
and step 300, the application client sends a service request to the JSP/Servlet component module.
And 301, after receiving the service request of the application client, the JSP/Servlet component module analyzes the service request and submits the service request to the EJB client in a service request object mode.
The creation code of the service request object and the service request initiated by the EJB client can be realized by the following codes:
v/creation of EJB client, the following string parameter being the invoked Business configuration object
EJBClient client＝new EJBClient
(″com.huawei.msp.bean.CommonFacadeBean″)；
V/define service request object
public class RequestValue implements CompositeValue
{
v/Call Bean object interface configuration name
private String requestCode；
// parameter List
private ArrayList paramList＝new ArrayList(2)；
/**
Default constructor
*/
public RequestValue()
{
requestCode＝Constant.CONST_EMPTY；
}
/**
Obtaining calling Bean object interface configuration name
*@return String
*/
public String getRequestCode()
{
return this.requestCode；
}
/**
Input parameter list of get request interface
*@return ArrayList
*/
public ArrayList getParamList()
{
return this.paramList；
}
/**
Setting and calling Bean object interface configuration name
*@param requestCode String
*/
public void setRequestCode(String requestCode)
{
this.requestCode＝requestCode；
}
/**
Setting parameters to request object
*@param param Object
*/
public void addParam(Object param)
{
this.paramList.add(param)；
}
}
V/construct service request object and assign value
RequestValue request＝new RequestValue()；
request.setRequestCode(″TestBean.query″)；
request.addParam(″2001021823231″)；
V/initiate service request
Client.callService(request)；
Step 302, after the EJB client analyzes the service request object information, the EJB client sends the service request to the service request proxy module.
The EJB client analyzes the message of the service request object and remotely calls a service request proxy interface in an RMI-IIOP (Remote method invocation Internet Inter-ORB Protocol) Protocol mode; the method comprises the steps of firstly providing JNDI (Java Naming and Directory Interface) service through an application server to obtain a Home Interface of a service request proxy, then establishing a remote operation Interface of the service request proxy through the Home Interface, and finally calling the service request proxy Interface.
When the EJB client calls the service logic, the service object is not directly called, but the service logic is called by proxy distribution of the service request proxy module. Therefore, when the EJB client sends a service request, a strict service request information format needs to be defined, including the class path identifier, the method identifier, and the parameter information of the service object. An example of code is as follows:
// get Facade (local) Home object instance
Object object＝Context.lookup(className，jndiName)；
V/through mapping mode, creating FacadeBean object remote instance by Home object
DelegateEJB delegate＝(DelegateEJB)BeanUtil.invokeMethod(object，″create″，null)；
// calling EJB component's service agent interface
Delegate.callService(request)；
Step 303, after receiving the remote invocation request, the service request proxy module sends the service request information to the service object information configuration module to obtain the configuration information of the service request object.
The service request agent module analyzes the service request information of the client to obtain the class path identification, the method identification and the parameter information of the service object.
The service object information configuration module loads the configuration information of the corresponding service object according to the class path identifier 'TestBean' and the method identifier 'query' specified by the service request information, and the information is returned to the service request agent module after being stored in an XML file format or a database form. The service object configuration information includes a class path name, a method name and a transaction attribute of the service object. Each configured business object can be associated with a unique identifier, and business declaration information of the method and the method of the business object is maintained under the business object. The code example of the configuration information of the queryTestInfo of the query method for loading the group user management service class is as follows:
<？xml version＝″1.0″encoding＝″UTF-8″？>
<config>
<module id＝″common″>
<bean id＝″TestBean″name＝″com.huawei.test.bean.TestBean″>
<method id＝″query″name＝″queryTestInfo″transaction＝″true″/>
</bean>
</module>
</config>
in an example, < Bean id ═ TestBean "name ═ com.huawei.test.bean.testbean" > identifies the configuration of the business Bean object, "TestBean" is an object configuration identifier, and "com.huawei.test.bean.testbean" is a class path name that identifies the corresponding class; "query" name "transaction" false "/> is method configuration information," query "is a method configuration identifier, and" queryTestInfo "is a method name. In the request object, the actual request information is replaced by the identification call sign, so that the 'testbean.query' identifies the methods of the service object com.
Step 304, the service request agent module obtains the service object instance in the service object pooling module.
And the service request agent module acquires the corresponding service object instance from the service object pooling module containing a plurality of service object instances according to the class path name and the method name of the service object.
In order to improve the service object request efficiency, the service object is added with a function of cache pooling. According to the service object configuration information provided by the service object information configuration module, the service object pooling module automatically loads all service object classes through a class loader (ClassLoader) in the Java virtual machine when the system is initialized, then initializes the service object according to the definition of the buffer pool in the service object pooling module, and instantiates the service object through a reflection mechanism of Java. The definition of the buffer pool comprises the implementation principle and architecture of the buffer pool and configuration information of relevant buffer pool specifications, wherein the main specifications of the buffer pool comprise the initialized number and the maximum buffer number of the business objects. When calling the client, the service request agent module can quickly locate the corresponding service object instance in the service object pooling module according to the configuration information provided by the information configuration module.
If the business object instance already exists in the business object pooling module and the state is idle, directly returning the reference of the object instance to the business request agent module for calling the business method, and simultaneously setting the state of the object to be busy; if the service object instance state is busy, determining the reference mode of the instance according to the service quality requirement level of the service request, and if the quality requirement is low, waiting for the reference when the service object state is idle; if the quality requirement level is higher, or the service object instance does not exist in the service object pooling module, an instance of the service request object is created in a Java reflection manner, stored in a buffer pool, and the instance reference is transmitted to the service request proxy module, and the state is also set to be busy (implementation of the instance structure and acquisition of the method object, please refer to a Java application programming Interface-API (application programming Interface-API) provided by Sun, which is not described in detail herein).
And the service object instance is not deleted along with the service end of the client, after the calling of the service object instance is finished, the service object reference is returned and stored in the service object pooling module, and meanwhile, the state of the service object instance is set to be idle. The buffer mechanism of the business object reduces the frequent creation and destruction of the business object and realizes the persistent management of the business object.
Step 305, the service request agent module locates the method object of the service object and the transaction attribute of the method object according to the obtained service object instance.
Step 306, the service request proxy module initiates a service call request to the service object pooling module.
After receiving the service calling request, the service object pooling module acquires relevant service information from the database, and the service request proxy module calls a method of the service object instance according to the acquired transaction attribute information of the service object instance, the method object and the method object; an example of code is as follows:
assume that the TestBean is implemented as follows:
public class TestBean implements BsnBean
{
public List queryTestInfo(String testid)throws PException
{
List list＝null；
// service logic implementation
return list；
}
}
Then according to the business object and method returned from the above steps, the calling mode actually through the reflection mechanism is as follows:
// Start-up Process
UserTransaction userTransaction＝null；
If(transaction)
{
userTransaction＝getTransaction(methods)；
userTransaction.begin()；
}
// method invocation
Object result＝method.(testBean，new String[]{“2001021823231”})；
// committing a transaction
If(userTransaction！＝null)
{
userTransaction.commit()；
}
Step 307, the service object pooling module returns the service processing result to the service request agent module.
And step 308, the service request agent module returns the service processing result to the EJB client.
Step 309, the EJB client returns the service processing result to the application client.
In the invention, the transaction management of the business method adopts a self-defined transaction declaration processing mechanism and can be realized by the following two ways:
1. and when the service request agent module is deployed, the declaration attribute of the method is the container transaction support, and all service logic calls executed by the service request agent module can obtain the transaction guarantee of the container. If the service logic is called by the JSP/Servlet technology, the service logic is operated in the Web container of J2EE to obtain the transaction guarantee of the Web container; if the business logic is called by the EJB technology, the business logic runs in the EJB container of J2EE to obtain the transaction guarantee of the EJB container.
2. When the business request agent module is deployed, the declaration attribute of the method is the Bean self-management business, at the moment, the business request agent module can declare according to the business in the configuration information, starts the business before calling the method, and submits or rolls back the business after the method is executed, so that the function of the Bean self-management business is achieved.
If there is no declarative attribute of the method, then the business process does not provide transaction management, reducing consumption of container resources.
In conclusion, the invention simplifies the design of the EJB component, reduces the complexity of development and deployment of the J2EE system, and also reduces the complexity of client application; the coupling between the presentation layer and the service logic layer is reduced by adopting a configuration mapping mechanism of the service object; in addition, the invention provides a user-defined transaction processing mechanism of the method object, simplifies the transaction management in the service development process and improves the working efficiency of the J2EE system.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (15)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610086757A CN1967485B (en) | 2006-06-20 | 2006-06-20 | A method and system for realizing J2EE application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610086757A CN1967485B (en) | 2006-06-20 | 2006-06-20 | A method and system for realizing J2EE application |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1967485A CN1967485A (en) | 2007-05-23 |
| CN1967485B true CN1967485B (en) | 2010-05-12 |
Family
ID=38076275
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200610086757A Expired - Fee Related CN1967485B (en) | 2006-06-20 | 2006-06-20 | A method and system for realizing J2EE application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1967485B (en) |
Families Citing this family (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100504773C (en) * | 2007-06-08 | 2009-06-24 | 北京大学 | Application server public service loose coupling access method |
| CN101478425B (en) * | 2008-12-31 | 2015-05-06 | 深圳市同洲电子股份有限公司 | Method and system for network management proxy |
| CN102026233A (en) * | 2010-12-03 | 2011-04-20 | 中兴通讯股份有限公司 | Method and device for realizing telecommunication equipment version compatibility |
| CN102841906B (en) * | 2011-06-24 | 2016-12-07 | 阿里巴巴集团控股有限公司 | The transaction processing system of a kind of integration and transaction processing method |
| CN103246547B (en) * | 2012-02-14 | 2018-09-04 | 武汉亿阳信通科技有限公司 | The method and system of remote invocation of objects |
| CN103152433B (en) * | 2013-01-14 | 2017-12-05 | 广东电子工业研究院有限公司 | A kind of use, interaction and the request processing method at Distributed Services end |
| CN103944956B (en) * | 2014-03-10 | 2017-06-20 | 浙江大学 | Web service broker method |
| CN105635208A (en) * | 2014-10-30 | 2016-06-01 | 阿里巴巴集团控股有限公司 | Business processing method and device |
| CN106598554B (en) * | 2015-10-14 | 2021-03-23 | 上海汽车集团股份有限公司 | A code generation device |
| CN105391785A (en) * | 2015-11-25 | 2016-03-09 | 广州华多网络科技有限公司 | Method for processing service message and server |
| CN105516266B (en) * | 2015-11-30 | 2019-06-11 | 华为技术有限公司 | A business monitoring method, system and related equipment |
| CN106095886B (en) * | 2016-06-03 | 2020-10-09 | 腾讯科技（深圳）有限公司 | Data processing method and device |
| CN108255545B (en) * | 2016-12-28 | 2022-09-02 | 阿里巴巴集团控股有限公司 | Function calling method and device between components and modular architecture system |
| CN107133055B (en) * | 2017-06-07 | 2020-04-24 | 百卓网络科技有限公司 | Method for realizing customized development based on ClassLoader |
| CN108628605A (en) * | 2018-04-28 | 2018-10-09 | 百度在线网络技术（北京）有限公司 | Stream data processing method, device, server and medium |
| CN113535253B (en) * | 2020-04-16 | 2025-10-10 | 腾讯科技（深圳）有限公司 | A business processing system, a business processing method and related devices |
-
2006
- 2006-06-20 CN CN200610086757A patent/CN1967485B/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN1967485A (en) | 2007-05-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1967485B (en) | A method and system for realizing J2EE application | |
| US11171897B2 (en) | Method and apparatus for composite user interface generation | |
| CN100407154C (en) | Systems and methods for modeling and dynamically deploying services in a distributed network architecture | |
| CN101408899B (en) | Method and apparatus for switching website multiple data sources | |
| US8024743B2 (en) | Connection of clients for management of systems | |
| US7593994B2 (en) | Generating a dynamic web service and dynamic service surrogate for legacy application components | |
| US20020004850A1 (en) | System and method of providing a messaging engine for an enterprise javabeans enabled server to achieve container managed asynchronous functionality | |
| JPH1083308A (en) | Stub search and loading subsystem, stub search and loading method, and stub search and loading recording medium | |
| WO2002033545A2 (en) | Pluggable instantiable distributed objects | |
| US20050172295A1 (en) | System and method for adaptable provisioning of generic application content | |
| US7536688B2 (en) | Segmented virtual machine | |
| US8387039B2 (en) | System and method for customized provisioning of application content | |
| Zachariadis et al. | Satin: a component model for mobile self organisation | |
| WO2007001640A2 (en) | Data centric workflows | |
| CN113806104A (en) | Interface access request processing method, API gateway, server and system | |
| US11379201B2 (en) | Wrapping method, registration method, device, and rendering apparatus | |
| US8458716B2 (en) | Enterprise resource planning with asynchronous notifications of background processing events | |
| WO2001035242A1 (en) | Highly distributed computer server architecture and operating system | |
| US20250045067A1 (en) | Hybrid multi-tenant framework for reconfiguring software components | |
| CN103677842A (en) | Software tool configuration type integrated expansion calling method and system | |
| CN109669793B (en) | Middleware in-process object call method | |
| CN100595732C (en) | A Method of Obtaining Class Loading Information in Application Server | |
| CN113312031A (en) | Naming service interface of software communication system structure | |
| Sengul et al. | Building a service provisioning system using the Enterprise JavaBean framework | |
| US7472174B2 (en) | Abstract mechanism for constructing commands for the command pattern |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100512 Termination date: 20120620 |