Automated REST API Code Generation from SOAP Schemas

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developers face complexity and inefficiency when manually creating and mapping between SOAP and REST APIs, particularly due to the need for extensive field mapping and handling of XML and JSON formats, with no single tool providing a comprehensive solution for generating integration code.

Innovation Solution

A system and method for automatically generating a Maven project that includes REST API code artifacts such as JSON Schema, request and response mapping, and development code in the native language of the integration platform, allowing for the creation of REST APIs from SOAP or REST schema definitions with minimal programming.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If developers manually create and map between SOAP and REST APIs, then integration functionality is achieved, but development complexity and time consumption increase significantly

Engineering Contradiction:
ImproveAPI development speedVSAvoiddevelopment complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by automatically generating field mappings between SOAP and REST APIs before developers need to use them. The code generator creates the integration code in advance based on schema definitions, eliminating the need for developers to manually create complex mappings during the integration process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses copying by generating code templates and field mappings automatically from schema definitions. Instead of requiring developers to write each integration from scratch, the system creates reusable code templates that can be copied and adapted, significantly reducing development effort and complexity.

Inventive Principle:
Principle #26Copying

2Manufacturing precision

If comprehensive field mapping and format conversion are performed manually, then integration accuracy improves, but human error increases due to tedious work

Engineering Contradiction:
Improveintegration accuracyVSAvoiderror rate
Core Design Contradiction:
Manufacturing precisionVSReliability

Solution Approach 1:

The system implements self-service by automatically generating field mappings and performing format conversions without human intervention. The code generator autonomously analyzes schema definitions and creates the integration code, eliminating manual errors while maintaining high accuracy in field mapping and data format conversion.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If multiple separate tools are used for different parts of API integration, then specialized functionality is achieved, but overall process complexity increases

Engineering Contradiction:
Improvetool functionalityVSAvoidnumber of tools
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system merges multiple separate tools into a single unified code generator that handles schema definition, field mapping, format conversion, and code generation all in one place. This consolidation maintains the specialized functionality needed for each task while eliminating the complexity of coordinating multiple separate tools.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The code generator implements universality by providing multi-functional capabilities within a single tool. It can handle both SOAP and REST APIs, perform various format conversions (XML, JSON, CSV), and generate integration code for different programming languages, replacing the need for multiple specialized tools.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Productivity

If extensive field mapping is performed manually, then complete integration is achieved, but development time increases

Engineering Contradiction:
Improveintegration speedVSAvoiddevelopment time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system replaces the mechanical manual process of field mapping with an automated code generation system. Instead of developers manually analyzing and mapping each field between SOAP and REST APIs, the system uses automated algorithms to perform this task, dramatically reducing development time while maintaining complete integration coverage.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS10331422B1System and method for generating API devlopment code for integrating platforms
Publication Date: 2019.06.25 DIAMOND EDGE IT INC
  • US10331422B1 patent drawing
  • US10331422B1 patent drawing
  • US10331422B1 patent drawing

AI summary

A system for creating generating a Maven project that functions as a reusable API in an application network is provided. The Maven project is defined as a REST API. The system has a hardware processor configured to perform a predefined set of basic operations in response to receiving a corresponding input, a generator in communication with the hardware processor, the generator configured to create code artifacts to communicate to a SOAP or REST API based on the user input, wherein the generator is further configured to create data mappings to map the differences between fields and data format languages defined by the schema definitions. A method for generating a REST API is also disclosed.