XINS application was designed to be an open-source Web Services technology, supporting SOAP, XML-RPC and REST. It consists mainly of an XML-based specification format and a Java-based implementation framework.
From its specifications, XINS can generate HTML, WSDL, client-side code, server-side code and test forms. Users do not require knowledge of any complex formats, such as XML Schema.
XINS is a Web Services framework. XINS is a technology used to define, create and invoke remote APIs. APIs are defined in a simple XML format.
Then the specifications in HTML and in OpenDocument format, the test forms, the WSDL included the XML Schema, the Java client and server side code are generated from the specifications.
APIs accept SOAP, REST, XML-RPC and more. Java, PHP, Perl and AJAX examples are provided. XINS has also command to generate unit tests, stubs or to run the API. XINS main focus is simplicity and usability.
XINS is a technology that supports you in defining, implementing and invoking remote HTTP-based APIs. Definition is done using a simple XML format. From this XML, XINS generates HTML-based documentation, along with Java code for both the client- and the server-side.
The XINS/Java Server Framework is to a XINS API implementation what a Servlet Container is for a servlet. It is a sandbox for your API implementation. It checks incoming requests and outgoing responses to confirm that they conform to the specifications. It features transaction logging, unique log documentation, access control (ACLs) and diagnostic context identifiers, etc.
Besides that, XINS also offers a XINS/Java Client Framework, which offers an easy means of calling a XINS API implementation. It offers client-side load-balancing, fail-over and support for different kinds of time-outs. All of this comes with the same high-quality logging.
· Java Development Kit
· Apache Ant
What's New in This Release: [ read full changelog ]
· Added possibility to define a caching time for the response to avoid unneeded requests. See HttpClient Cache for client side handling.
· Added possibility to return not modified to avoid unneeded data transfer and unneeded parsing/unparsing/validation/convertion.
· Fixed function name in backpack for standard calling convention.
· Added JSON-RPC 2.0 calling convention.
· New standard error codes returned to client: _FunctionNotSpecified, _FunctionNotFound, _InvalidRequestFormat, _NotAllowed, _DisabledAPI.