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

Application Server - Assistant program and property to write the xsi:type for each SOAP response XML element

IP.com Disclosure Number: IPCOM000244702D
Publication Date: 2016-Jan-06
Document File: 3 page(s) / 51K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article proposes a solution where an Application Server program, read the predefine application server property (write xsi:type) value for any web application (web service) which installed on application server to determine whether to write the xsi:type for each SOAP response XML element or not. Application server program add the xsi:type for each SOAP response XML element if property value is 'true' and return the response back to the web service client else program return the application generated response to the web service client. This solution is for all application servers like Tomcat, Weblogic and WebSphere Application Server etc...

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

Page 01 of 3

Application Server - Assistant program and property to write the xsi :type for each SOAP response XML element

In the XML document if we want to use a type other than the one explicitly specified in the schema then we have to let the parser know which type we are using. This is done using the xsi:type attribute. The xsi:type attribute is used to indicate to the schema validator that the real type of a particular instance of an element is not the element's declared type but rather a sub-type derived from the declared type. Apache CXF or any other web service framework which use either Aegis or JAXB data bindings, only write the xsi:type when it's actually needed. Basically, if the xsi:type is identical to what the schema says it would be, it doesn't write it out. However sometimes its client requirement to write the xsi:type for each SOAP response XML element.

This invention proposes a solution where an Application Server program, read the predefine application server property (write xsi:type) value for any web application (web service) which installed on application server to determine whether to write the xsi:type for each SOAP response XML element or not. Application server program add the xsi:type for each SOAP response XML element if property value is 'true' and return the response back to the web service client else program return the application generated response to the web service client. This solution is for all application servers like Tomcat, Weblogic and WebSphere Application Server etc...

The proposed solution to the problem described above is an application server program that runs in the background on the application server and an application server property. Think of this program as an "assistant". This program read the "write xsi:type" property value and add the xsi:type for each SOAP response XML element if property value is 'true' based on schema definition stored on the server.

The assistant program will run as a background application. The "write xsi:type" property (JVM property or application server variable) will be available on application server which is associated with installed web service application. The possible values of this property are 'true' and 'false' and the default property value is 'false'. A server path will be associated with this property where schema definition is stored. The assistant program read the property value and add the xsi:type for each SOAP response XML element if property value is 'true' based on schema definition stored on the server.

High Level Solution diagram -

Below are high level steps of proposed solution -

Client access the web service application installed on application server using web service client

...