Generalized Connector for Dynamic Middleware to EJB Bridging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in creating a connector between middleware applications like Vitria and Enterprise Java Bean (EJB) software objects, requiring explicit knowledge of underlying functionality and leading to errors and inefficiencies due to the need for detailed, time-consuming code writing.
Innovation Solution
A method and system using representations of middleware data structures to dynamically bridge a middleware application to an EJB software object API without knowledge of the underlying functionality, employing a generalized connector mechanism that recognizes events and invokes appropriate EJB methods automatically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If explicit code is written to control interaction with EJB software objects, then the connector can interact with the application system, but the development process becomes excessively time-consuming and detail-oriented
Solution Approach 1:
The connector enables self-service by automatically determining which EJB software object is associated with an event object and invoking appropriate methods without requiring explicit programming. The system uses the event object's class name to dynamically locate and interact with the corresponding EJB object, eliminating the need for detailed manual code writing while maintaining full interaction capability.
2Reliability
If explicit knowledge of underlying functionality is required, then the connector can be created, but the process becomes excessively detail-oriented and subject to error
Solution Approach 1:
The event object serves as an intermediary that bridges the middleware application and the EJB software object. By using the event object's class name to dynamically determine the associated EJB object, the system eliminates the need for explicit knowledge of underlying functionality. This intermediary approach reduces errors by automating the mapping process while maintaining system reliability.
Solution Approach 2:
The system dynamically changes parameters at runtime by using the event object's class name to determine which EJB software object to invoke. This parameter-driven approach allows the connector to adapt to different EJB objects without requiring explicit programming knowledge, reducing both complexity and error potential while maintaining reliable interaction.
3Productivity
If a generalized connector mechanism is used to dynamically bridge middleware to EJB objects, then efficiency increases and errors reduce, but knowledge of underlying functionality is not required
Solution Approach 1:
The generalized connector mechanism enables self-service by automatically using the event object's class name to determine the associated EJB software object. This eliminates the need for developers to possess knowledge of underlying EJB functionality while maintaining high productivity. The system serves itself by dynamically resolving object mappings without human intervention or explicit programming.
Data Source
AI summary
A method is described for constructing a generalized connector for use in an object-oriented program system, the connector being a middleware service logic mechanism between an event monitor and transmission sub-system and an application system having an application system Application Program Interface (API), wherein the connector can recognize events provided by the event monitor as event objects and can automatically determine which corresponding ENTERPRISE JAVA BEAN (EJB) software object is associated with the event object, and can invoke methods on the EJB software object in a specified order, and can collect the results of the method invocations for return to the event monitor. A connector for performing these functions is also described.