Automated SOAP Web Service Code Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing methods for developing and deploying SOAP web services are inefficient due to repetitive development, testing, and deployment efforts, leading to wasted time and delayed service availability, as services often overlap, requiring automation and simplification to reduce repetition and speed up delivery.

Innovation Solution

A computerized method and system that automatically generates source code for SOAP web services by selecting the type and inputs/outputs, validating inputs, defining conditions, and mapping outputs, which includes generating a jar file for deployment and storing configurations in XML format, allowing for the creation and alteration of web services, including data verification services across various data sources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual development and deployment methods are used for SOAP web services, then services can be created with custom functionality, but development time and deployment time are excessive due to repetitive efforts

Engineering Contradiction:
Improveservice delivery speedVSAvoiddevelopment time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-defining service templates, input/output schemas, and deployment configurations before actual service creation. This allows automatic generation of service code and deployment artifacts, eliminating repetitive manual development and deployment efforts while maintaining custom functionality.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If manual service development processes are used, then services can be customized, but repetition across overlapping services wastes time and delays availability

Engineering Contradiction:
Improveservice customization capabilityVSAvoidservice availability time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system implements universality through service templates and configurable parameters that can be reused across multiple services. A single template can generate different services by varying input/output definitions and configuration settings, eliminating repetitive customization work while maintaining service-specific functionality and reducing time to market.

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

3Productivity

If automated service generation is implemented, then development time is reduced, but the complexity of the generation system increases

Engineering Contradiction:
Improveservice creation efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary layer consisting of service templates, configuration files, and generation rules that mediate between user requirements and actual service implementation. This intermediary structure manages the complexity of automated generation by providing standardized interfaces and predefined patterns, reducing the apparent complexity for users while maintaining high productivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11829732B2Simple object application protocol web service applications
Publication Date: 2023.11.28 ELM INC
  • US11829732B2 patent drawing
  • US11829732B2 patent drawing
  • US11829732B2 patent drawing

AI summary

Methods, systems, and computer readable media to automatically generate source code for simple object application protocol (SOAP) web services are described. The method can include selecting a type of web service and a web service. The method can also include selecting one or more inputs or one or more outputs corresponding to the type of the selected web service. The method can further include defining one or more conditions for the one or more outputs. The method can also include automatically generating a source code file for the web service based on one or more of the type of web service, the one or more inputs, the one or more outputs, or the one or more conditions, and deploying the source code file to a server. The method can further include generating a document that lists one or more specifications of the web service.