Container-less JSP Template Invocation via ESF

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing JSP technology requires a J2EE container for template invocation, limiting its use to web applications and restricting seamless integration with non-web applications, as well as relying on specific protocols and frameworks.

Innovation Solution

The implementation of eBay Server Fragments (ESF) allows JSP templates to be invoked without a J2EE container, using Java 5.0 annotations instead of XML declarations, providing a platform for standalone applications to leverage JSP templating features, including support for major JSP abstractions and adapters for existing servlet constructs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If JSP templates are invoked using traditional J2EE container, then JSP templating functionality is achieved, but dependency on web framework and container is created

Engineering Contradiction:

Improveapplication type supportVSAvoidcontainer dependency

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the JSP templating functionality from the J2EE container environment, allowing JSP templates to be invoked directly as Java classes without requiring a web container. This separation enables JSP templates to be used in standalone applications, batch processing, and other non-web contexts while maintaining the templating capabilities.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the JSP processing into distinct components: template definition, template compilation, and template execution. By making these components independently accessible through a Java API, the system eliminates the need for a monolithic J2EE container while preserving JSP templating functionality across different application types.

Inventive Principle:

Principle #1Segmentation

2Ease of manufacture

If XML declarations are used for JSP templates, then template structure is defined, but complexity and verbosity increase

Engineering Contradiction:

Improvetemplate creationVSAvoidXML syntax requirement

Core Design Contradiction:

Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent replaces the XML-based declaration system with Java 5.0 annotations. Instead of using XML syntax to define template structure and metadata, developers can use straightforward Java annotations directly on template classes, reducing verbosity and eliminating the need to learn XML syntax for JSP template definitions.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If JSP is tightly coupled with servlet technology, then web application integration is achieved, but integration with non-web applications is restricted

Engineering Contradiction:

Improveweb application integrationVSAvoidframework integration

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal JSP template invocation mechanism that works across multiple contexts: web applications, standalone applications, batch processing, and other frameworks. The Java API and annotation-based approach provide a common interface that adapts to different execution environments without requiring tight coupling to servlet technology.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9727397B2Container-less JSP template

Publication Date: 2017.08.08 PAYPAL INC

AI summary

A container-less JSP system is provided. An example container-less JSP system comprises a detector, a trigger module, and an invoker. The detector may be configured to detect a request initiated by a client application to invoke a JSP template. The request is a protocol-neutral Java™ interface. The trigger module may be configured to trigger the protocol-neutral Java™ interface to invoke the JSP template. The invoker may be configured to invoke the JSP template.