• Journal of Digital Convergence
• /
• v.10 no.8
• /
• pp.219-224
• /
• 2012

This paper aims to design and realize movie reservation system based EJB 3.0 enterprise for standardization. Non EJB and the EJB architecture to resolve the problem with benefits to support the new architecture is a lightweight container architecture. This architecture, such as the EJB, but not heavy, to provide all of the architecture is possible. The lightweight container architecture is most often used in business EJB 3.0 is well-known architecture. Therefore, this research has the Non EJB and the EJB to solve the advantages and disadvantages developed to support the latest EJB 3.0 architecture based on the design and implementation of a movie reservation system.

• Journal of Digital Convergence
• /
• v.12 no.3
• /
• pp.263-268
• /
• 2014

The purpose of this study is to provide a quantitative evaluation index of object-oriented software development productivity for EJB 3.0 and EJB 3.1. A lightweight container architecture is a newly-developed architecture in order to solve demerits that N-Tiers enterprise architecture has and to support merits therein. A lightweight container architecture is not as heavy as EJB(Enterprise JavaBeans) architecture is, whereas it provides all the functionality of the EJB container. However, there have been insufficient studies on a performance evaluation of EJB 3.0 and EJB 3.1 on an identical platform. Since a quantitative analysis has been performed only with respect to a partial LoC(Line of Code) analysis, there have been insufficient objective evaluation indeces and guidelines for a new specification released. Accordingly, there has been limited evaluation of software development productivity and on new innovations in a project. Therefore, this study designed and implemented a movie reservation system in EJB 3.0 and EJB 3.1, which was based on the same development platform environment. This study then intends to provide evaluation guidelines for an objective software development productivity cl LoC(Lineand standardization thereof by development platform environment.

• 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 Digital Convergence
• /
• v.10 no.3
• /
• pp.137-142
• /
• 2012

This paper proposes a software development guidance and an evaluation index for the productivity related to Spring 2.5 and EJB 3.0 with same lightweight container architecture. Spring is a known successful open source standard model for lightweight container architecture. EJB in an enterprise environment as a standard framework is most commonly used in production. However, there is no comparison research about the performance of Spring 2.5 and EJB 3.0 Framework 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 the software. In this study, the development platform environment based on the same pilot system Spring 2.5 and EJB 3.0 framework is in the design and implementation. In addition, comparison and standardization of software development productivity assessment is to provide guidance.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.11b
• /
• pp.982-984
• /
• 2005

효과적인 어플리케이션 로그처리는 어플리케이션 개발 및 운영 시에 매우 중요한 요소 중에 하나이다. 파일이나 콘솔을 이용하여 동기식으로 처리되는 일반적인 로그 서비스는 동시에 대량의 로그를 처리해야 할 경우 시스템에 많은 부하를 주게 되는 문제점이 있다. 이를 해결하기 위해서는 클라이언트가 지연 없이 로그를 남길 수 있는 비동기식 로그서비스가 필요하다. 이 논문에서는 비동기식 로그서비스 구현을 통해서 Message-Driven POJO(MDP) 구현 기술을 소개하고 최근에 소개된 EJB 3.0 Message Driven Bean(MDB) 기술과 비교 분석해 보도록 한다.