Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method for Adapting XML Schema Definitions for Legacy Systems

IP.com Disclosure Number: IPCOM000219541D
Publication Date: 2012-Jul-05
Document File: 3 page(s) / 26K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method is provided for adapting XML schema definition to comply with legacy systems that require fixed field value lengths by padding default characters within the XML schema definition.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 01 of 3

Method for Adapting XML Schema Definitions for Legacy Systems

Disclosed is a method for adapting XML schema definition to comply with legacy systems to make them Service Oriented Architecture compliant.

The disclosed method enables developers to use XML schema definitions (XSD's) in legacy systems, such as mainframes, that use programming languages having field value length restrictions. Accordingly, the method automatically pads character fields with spaces and prefixes integers with zeroes instead of doing it programmatically. The automatic padding is achieved by adding keywords in XSD's for padding of spaces and zeroes. The added keywords are used to define restrictions in the XML schema. Each of the added keywords helps adapt the XSDs suitably for the legacy systems. The disclosed method thus may be used by XML engines to provide developers a way to pad XML fields at runtime instead of doing it manually inside the code.

XSD's have keywords that may be used to retain whitespaces, remove whitespaces, and restrict the fields to certain values and maximum lengths. However, in order to pad string fields with spaces or prefix zeroes to numbers, the disclosed method provides a number of keywords to adapt the XSD's automatically. In an embodiment, the method provides 3 keywords, namely:


fixedLength - adapts the XSD to be padded to the exact number of characters


leftPad - indicates the padding to be performed on the left side, before the first character. Therefore, use of this keyword may be made default for integers of fixed length


rightPad - indicates the padding to be performed on the right side, after the last character. Therefore, use of this keyword may be made default for strings of fixed length.

Thus, if the value is a string then it is padded with spaces and if it is numeric then it is prefixed with zeroes before being sent over to the legacy systems.

For example, according to the embodiment as disclosed, for fields defined in a legacy CICS program as:

EMPID - integer, length = 5

FNAME - string, length = 10
LNAME - string, length = 10

the XSD needs to be...