• Proceedings of the Korean Information Science Society Conference
• /
• 2002.10e
• /
• pp.148-150
• /
• 2002

EJB(Enterprise Java Bean)에서는 데이터베이스나 JMS(Java Message Service), 메일, ERP와 같은 외부 시스템 자원을 사용하기 위해 EJB 스펙은 JCA(Java Connector Architecture) 사용을 권장하고 있다. 본 논문에서는 E504(Enterprise 504) EJB 컨테이너가사용하는 여러 가지 자원 중 데이터베이스 커넥션에 초점을 맞추어 EJB 스펙에서 논의하고있는 리소스 관리 요구 사항과 JCA를 이용한 데이터베이스 커넥션 관리 방법 및 빈에서 발생 가능한 커넥션 요청 모델에 대해 논의한다.

• 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 KIISE:Software and Applications
• /
• v.30 no.12
• /
• pp.1185-1192
• /
• 2003

In the component assembly and composition technique of software architecture, It is operated that the existing composition techniques based on architecture, ACME, Wright etc., used in FIFO with the direct connection structure between components through connector's Role. But, when the non-synchronizing request of components that have different characteristics occurs, the FIFO techniques is applied to the connector is difficult to process and operate effectively because of the high performance component waiting the sequence order if the low performance component is allocated first. Thus, the allocated request process according to the priority considering the characteristics of each call components in connector is necessary to improve the operation of assembled component. In this research, we extend the connector part that is available in multiplex connection structure based on existent Wright specification. For service process requested from component, the connector part is designed and implemented to operating with priority sequence through calculating the weight of CPU use rate, bean requesting process time and memory use rate among the efficiency elements of assembled components. To verify the efficiency if this designed connector, we implemented 20 samples EJB components that have different efficiency characteristics and applied these samples components to designed connector. The operating results with this designed connector show that the efficient operation of whole system is possible though the processing time takes 481ms more than the time of the existing FIFO techniques.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.7 no.5
• /
• pp.1089-1094
• /
• 2003

Recently, Software development method supported CBD is applied with many concern and is researched with part of application and composition based-on architecture effectively use it. Effectively, C2 architecture has been concern with the point of component composition method based-on message driven for supported GUI. But, In case of classified sequence in component and method call method in server component, component must be modified to apply it. Thus, In this paper, Message handling part with a part of C2 architecture change is locate in the message neither component not connector. So, Although method call method it can be composit and operate component for support Plug-and-Play without modification. Also, it's possible the more flexible message handling with parallel composition of component between message without classified sequence.