• Journal of KIISE:Software and Applications
• /
• v.36 no.4
• /
• pp.261-272
• /
• 2009

The EJB 3.0 specifications, which were improved in terms of performance and ease of development, were recently announced. Accordingly, for the EJB 3.0 application environment, developers generally prefer the gradual transformation of components whose performance must be improved to the complete transformation of all the EJB 2.1 components into EJB 3.0 components. Previous studies, however, did not consider the service of the application and did not ensure the compatibility and reusability of the components in the full replacement of EJB 3.0 due to the transformation using different specifications. This study proposed three transformation techniques that consider the service supported in the existing application, wherein the compatibility and reusability of the components are ensured in the case of the full replacement of EJB 3.0. The proposed transformation techniques are techniques for gradual transformation, such as direct transformation that directly connects components, indirect transformation that uses the EJB connector, and indirect template transformation wherein the template pattern is applied to the indirect transformation. The proposed transformation techniques were verified by comparing the reusability and processing capability of the components per second, and the standards for selecting a technique were provided based on the characteristics of the transformation into EJB 3.0 that were found in this study.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.31 no.3
• /
• pp.1-7
• /
• 2008

This paper proposes an object-oriented software development guidance and an evaluation index for the productivity related to EJB(Enterprise JavaBeans). EJB is a known successful standard model for LSDO(Large Size Distributed Object). However, there is no comparison research about the performance of EJB 2.0 and 3.0 with same identical platform. Quantitative analysis is supported as a part of LOC(Line Of Code) analysis. There is a limit to develop the updated software with no the specific evaluating index for the productivity of software. This work proposes an specific index for evaluating the productivity of new version EJB on a platform. Base on the result, the specific guidance of the developing software is obtained.

• Journal of KIISE:Computing Practices and Letters
• /
• v.7 no.5
• /
• pp.429-439
• /
• 2001

EJB(Enterprise JavaBeans), the cornerstone for J2EE(Java$^{TM}$ 2 Platform, Enterprise Edition), is a server-side component standard model. Recently, development of supporting tool for this component model becomes important and there are many tools for developing EJB. In this paper, we purpose to design Enterprise Beans by component model, and perform design and implementation of code generator which generates skeleton code for Enterprise Beans automatically. We also implement EJB deployer for deploying these on application server. The code generator can make a JAR file automatically. This JAR file is deployed on application server by EJB specification as well. Using this tool, developer can create and deploy of Enterprise Beans more fast and exactly.y.

• KSCI Review
• /
• v.8 no.1
• /
• pp.29-36
• /
• 2001

EJB application development environment is developing component support Object-Oriented distributed processing, it is component architecture for distributed arrangement. Application developed using EJB is component coupled for business program development easily. EJB is automatically sovled to security. resource Pooling, persistency, concurrency. transaction transparency. This Paper illustrate for EJB extract to EJB sufficient flexibility its development environment, and it was applicated remote university application domain.

• Proceedings of the Korean Information Science Society Conference
• /
• 2003.10c
• /
• pp.247-249
• /
• 2003

EJB(Enterprise Java Beans)는 웹 응용 서버 스펙인 J2EE(Java2 Enterprise Edition)의 핵심으로서, 비즈니스 업무를 웹 환경에서 컴포넌트 형태로 작성하여 재 사용성을 높이기 위한 서버 측 컴포넌트 프로그래밍 모델이다. EJB 2.1에서는 기존 EJB 2.0에 기술된 기능 이외에 웹 서비스, 타이머 서비스, EJB QL 업그레이드 등의 기능을 추가하였다. 타이머 서비스는 지정된 시간마다 EJB 빈의 특정 함수를 호출하는 기능이다. 또한, 타이머 서비스는 트랜잭션과 연관된 경우 해당 트랜잭션 컨텍스트(context) 내에서 타이머의 롤백(rollback)을 지원해야 하며, 시스템의 고장 후 재시작 시에 기존 타이머의 복구 기능을 지원해야 한다. 본 논문에서는 EJB 스펙 2.1에서 제시한 타이머 서비스의 요구 사항에 대해 알아보고, ETRI 에서 개발한 E504 EJB 서버에서 타이머 서비스를 구현한 방법에 대해 논의한다.

• Journal of Internet Computing and Services
• /
• v.2 no.5
• /
• pp.41-47
• /
• 2001

This paper deals with an EJB-based database agent(component) used to define workflow processes, which is a core function of the e-Chautauqua workflow management system that is an on-going research product. We describe about how to design and implement the EJB-based DB agent that is deployed on EJB server as a component. The agent is located between the build-time clients and the database system, and manages database accesses, such as retrieves and stores, from the workflow definition components. Through the EJB technology, we are able to accomplish a stable database agent that can be characterized by the distributed object management, reliable recovery mechanism from system failovers, reliable large-scale transaction management, and the security functions.

• Journal of KIISE:Software and Applications
• /
• v.30 no.12
• /
• pp.1172-1184
• /
• 2003

At present, new techniques based on different component reference models for the integration of component and system of different platforms, such as EJB and COM+, are introduced. The operation between the components in the identical component platform is realized by the composition at the source level. In case of the different component platform, however, it is impossible to use combined components in real condition although they are components of similar domain. In this paper we proposed a solution for the composition problem by using component transformation methodology based on model between EJB and COM+ components which are different components. For the composition between EJB and COM+ components, we compared and analyzed each reference model, then proposed the Virtual Component Model which is implementation independent and the Implementation Table for the mutual conversion. Reffering to the Virtual Component Model and the Implementation Table, we can generalize each Implementation model to the Virtual Component Model, make the Virtual Component Model which is implementation independent through the virtual component modeling, transform EJB and COM+ components selectively. Proposing the effective Model Transformation method to the different component platform, we can combine EJB and COM+ components.

• Proceedings of the Korean Information Science Society Conference
• /
• 2003.10c
• /
• pp.190-192
• /
• 2003

본 논문에서는 EJB 서버에 대한 제어 시스템 구현 방법에 관한 것으로써, 원격지에 분산되어 있는 EJB 서버를 관리 도구상에서 분산되어 있는 EJB 서버들을 마치 로컬상에서 제어하는 것과 동일하게 구동하고, 정지하며, 상태 정보를 모니터링 할 수 있는 원격 제어 시스템 구현에 대해 설명한다.

• Journal of Internet Computing and Services
• /
• v.16 no.2
• /
• pp.85-98
• /
• 2015

Component technologies which enable quickly and effectively to develop software have begun to come into the spotlight since early 1990s. Currently, a number of software development works are performed on the J2EE/EJB environment. However component testing is a very complicated task, in addition it requires more efforts than the previous Java class testing. Thus many developers do not perform sufficiently testing works. In this paper we propose an automatic testing method for EJB components based on the in-container testing strategy and implement a testing tool. Since our method builds automatically the test environment for EJB components, it is possible for developers or testers to save their time and efforts at the test preparation phase. Therefore we are convinced that the reliability of EJB components can be increased through sufficient testings with our method.

• Proceedings of the IEEK Conference
• /
• 2003.07d
• /
• pp.1613-1616
• /
• 2003

We will take a multitude EJB Design Patterns that you can harness to enhance your EJB Project today In this paper, we propose the EJB Based Entity Bean DBMS connecting system. Generally, EJB Based Entity Beans are respectively connected by DBMS. Therefore, for the this problems we suggest that Abstract Factory pattern uses DBMS connecting of Entity Beans. As a result, we evaluate MIF and CF in every class relationship.