Enterprise JavaBeans Components Research Articles

Research on Product Development Process Management for Virtual Enterprise

For a manufacturing enterprise to be competitive in constantly changing market environment, it is necessary to adopt a new model called agile manufacturing by organizing Virtual Enterprise. Aimed at developing a product development process management (PDPM) system for Virtual Enterprise, modeling of product development process is discussed and a union information model is proposed using Object Modeling Technique. Based on the J2EE platform, a framework of PDPM system is built up with a three-tiered architecture, which consists of several Enterprise JavaBeans components to ensure compatibility, distribution, and flexibility of the system. A PDPM system prototype is developed utilizing JAVA and has been validated in a simulated virtual enterprise environment.

Extending the OBJECTIVE Benchmark for Evaluation of Active Rules in a Distributed Component Integration Environment

This research presents a benchmark for the evaluation of active rules within a distributed component integration environment. The benchmark is based on the OBJECTIVE active database benchmark. Our work was specifically performed in the context of the Integration Rules (IRules) project that uses active rules for the integration of distributed software components, which are based on the Enterprise JavaBeans component model. In addition to mapping the test rules of the OBJECTIVE benchmark to the integration rules of the IRules system, we have extended the OBJECTIVE benchmark to test additional features of a component-based active rule system, such as the event detection time, the rule execution time related to the invocation of methods on components, asynchronous coupling modes, and the rule processor execution time under a heavy event load. Although the research presents specific performance evaluation results for the IRules project, the approach more generally demonstrates the manner in which an existing rule processing benchmark for a centralized environment can be adapted and extended for use in a rule-based approach to distributed component integration.

Component adaptation for event-based application integration using active rules

Enterprise applications integrate information and applications in a distributed, networked environment to develop a global application of interconnected components and applications. This paper presents the design and implementation of the wrappers generated to adapt components to a middleware environment that employs active rules to build an enterprise application using an event-driven approach to integrating distributed black-box components. The components adapted in this implementation are based on the Enterprise JavaBeans component model. An application integrator declares the components to be integrated, and may define additional attributes, relationships, and events to be used in the integration process. The metadata for the components to be integrated is used to adapt and enhance the black-box components through the use of wrappers. The wrappers act as a proxy to the black-box component. The adaptation of the wrappers provides for the storage of additional properties for component instances and for the detection of events within the components to generate event notifications. The wrappers are automatically generated from the component metadata using the Extensible Stylesheet Language. The design and implementation of the wrappers establishes a framework that supports an active approach to component-based software integration.

Component-oriented programming

Preface. 1. Introduction. 1.1 What is COP? 1.2 Why is COP important? 1.3 What is a component? 1.4 Hardware components and software components. 1.5 From OOP to COP. 1.6 Component-based software engineering. 1.7 Summary. 1.8 Self-review questions. 1.9 Exercises. 2. A Theory of Components. 2.1 Principles of COP. 2.2 Infrastructures of COP. 2.3 Component models. 2.4 Connection models. 2.5 Deployment models. 2.6 Unifying component technologies. 2.7 Summary. 2.8 Self-review questions. 2.9 Exercises. 3. COP with JavaBeans. 3.1 Overview of JavaBeans technology. 3.2 The component model of JavaBeans. 3.3 The connection model of JavaBeans. 3.4 The deployment model of JavaBeans. 3.5 Examples and lab practice. 3.6 Summary. 3.7 Self-review questions. 3.8 Exercises. 4. Enterprise JavaBeans Components. 4.1 The EJB a rchitecture. 4.2 The component model of EJB. 4.3 The connection model of EJB. 4.4 The deployment model of EJB. 4.5 Examples and lab practice. 4.6 Summary. 4.7 Self-review questions. 4.8 Exercises. 4.9 Programming exercises. 5. CORBA Components. 5.1 The COBRA component infrastructure. 5.2 The CORBA component model (CCM). 5.3 The connection model of CORBA and CCM. 5.4 The deployment model of CORBA and CCM. 5.5 Examples and lab practice. 5.6 Summary. 5.7 Self-review questions. 5.8 Exercises. 5.9 Programming exercises. 6. .NET Components. 6.1 The .NET framework. 6.2 The component model of .NET. 6.3 The connection model of .NET. 6.4 .NET component deployments. 6.5 Visual Studio .NET. 6.6 Examples and lab practice. 6.7 Summary. 6.8 Self-review questions. 6.9 Exercises. 6.10 Programming exercises. 7. COP with OSGi Components. 7.1 Overview of OSGi technology. 7.2 The component model of OSGi. 7.3 The connection model of OSGi. 7.4 The deployment model of OSGi. 7.5 Examples and lab practice. 7.6 Summary. 7.7 Self-review questions. 7.8 Exercises. 8. Web Services Components. 8.1 The Web Services framework. 8.2 The component model of Web Services. 8.3 The connection model of Web Services. 8.4 Web Services component deployment. 8.5 Examples and lab practice. 8.6 Summary. 8.7 Self-review questions. 8.8 Exercises. 8.9 Programming exercises. Appendix.

Visual Component Assembly and Tool Support Based on System

Component-based development leverages software reusability and reduces development costs. Enterprise JavaBeans (EJB) is a component model developed to reduce the complexity of software development and to facilitate reuse of components. However, EJB does not support component assembly by a plug-and-play technique due to the hard-wired composition at the code level. To cope with this problem, an architecture for EJB component assembly is defined at the abstract level and the inconsistency between the system architecture and its implementation must be eliminated at the implementation level. We propose a component-based application development tool named the COBALT assembler that supports the design and implementation of EJB component assembly by a plug-and-play technique based on the architecture style. The system architecture is first defined by the Architecture Description Language (ADL). The wrapper code and glue code are then generated for the assembly. After the consistency between the architecture and its implementation is checked, the assembled EJB components are deployed in an application server as a new composite component. We use the COBALT assembler for a shopping mall system and demonstrate that it can promote component reuse and leverage the system maintainability.

Saving the world from bad beans

The Enterprise JavaBeans (EJB) framework requires developers to preserve architectural integrity constraints when writing EJB components. Breaking these constraints allows components to violate the transaction protocol, bypass security mechanisms, disable object persistence, and be susceptible to malicious attacks from other EJBs. We present an object confinement discipline that allows static verification of components' integrity as they are deployed into an EJB server. The confinement rules are simple for developers to understand, require no annotation to the code of EJB components, and can be efficiently enforced in existing EJB servers.

Using JavaBeans components as accessors to Enterprise JavaBeans components

In this paper we describe how the use of JavaBeansTM components together with Enterprise JavaBeansTM (EJB) components can help to develop flexible, mission-critical applications. We show how an application can be structured into three conceptual tiers, and how the use of JavaBeans components on the middle tier can help develop applications that can run in different client/server environments (i.e., thin or thick clients). This eases the separation of server-side and client-side application development, each focusing on different problem domains. We also show that the additional level of indirection provided by using JavaBeans components as accessors to server-side business objects helps users of IBM SanFranciscoTM components to isolate their client-side application development from upcoming changes in the underlying back-end technology (i.e., the migration from today's SanFrancisco infrastructure toward future EJB-based releases of SanFrancisco).