Java EE to OSGi Integration via Gateway Bundle

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing approaches to integrate the Java EE platform with the OSGi platform require significant changes to application development and deployment, making it risky and costly to retrofit monolithic Java EE applications into the OSGi model, and do not support incremental modularization.

Innovation Solution

A system and method that allows Java EE applications to leverage the OSGi platform while maintaining existing development environments and processes, enabling incremental modularization and integration of OSGi features like modularity and service dynamism without requiring the Java EE server runtime to run on a modular platform.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If monolithic Java EE applications are retrofitted into the OSGi model, then modularity and service dynamism are improved, but development complexity and risk increase significantly

Engineering Contradiction:

ImprovemodularityVSAvoiddevelopment complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the monolithic Java EE application into multiple OSGi bundles that can be independently deployed and managed. Each bundle represents a modular unit with specific functionalities, allowing incremental adoption of OSGi architecture without requiring complete restructuring of the entire application.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer that enables Java EE applications to access OSGi services without requiring the Java EE server runtime to run on a modular platform. This intermediary mechanism allows seamless integration between the traditional Java EE environment and the OSGi modular architecture.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If monolithic Java EE applications are retrofitted into the OSGi model, then service dynamism is improved, but cost and risk increase

Engineering Contradiction:

Improveservice dynamismVSAvoidrisk

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent enables partial adoption of OSGi features by allowing specific components of the Java EE application to be modularized into OSGi bundles while the rest of the application continues to run in the traditional Java EE environment. This gradual approach reduces risk by allowing validation and rollback at each step.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The patent allows applications to prepare for modularization by configuring OSGi bundles and services in advance, testing modular components independently before full integration. This preliminary action enables risk mitigation through staged deployment and validation.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If Java EE applications are structured as OSGi bundles, then modularity is improved, but ease of operation deteriorates due to restructuring requirements

Engineering Contradiction:

ImprovemodularityVSAvoidease of deployment

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent creates a universal deployment mechanism that works with both traditional Java EE applications and OSGi bundles. The system can operate in multiple modes, allowing applications to be deployed as conventional war files or as OSGi bundles depending on the specific requirements, maintaining ease of operation while enabling modularity where needed.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9152384B2System and method for referencing a dynamic module system within a component oriented application development framework

Publication Date: 2015.10.06 ORACLE INT CORP

AI summary

A system and method can support a hybrid application development environment. The system allows a client application in the application runtime environment to obtain a reference to a framework instance for a dynamic module system. Furthermore, the system can configure a bundle in the dynamic module system to be a gateway bundle based on the framework instance, and the client application can access the dynamic module system using the gateway bundle.