Server Configuration Details

JiBX/WS specific configuration can be used for applications deployed as HTTP Servlets or in the TCP Server.

HTTP Servlet Usage

For HTTP, the JiBX/WS implementation uses a simple Java servlet for the server implementation of web services. This servlet can be bundled as part of an existing web application, or as a standalone application. Web applications that include JiBX/WS may be deployed to any ordinary servlet engine (such as Apache Tomcat, or Jetty), as well as to any J2EE application server.

There are two aspects to defining JiBX/WS services running over HTTP. The basic JiBX/WS servlet configuration lists the services to be included within a web application, while the service definition for each service provides the details of the ports and operations involved in that service.

The runtime dependencies must be included in the WEB-INF/lib directory of the web application, and any classes used by the actual web service(s) must also be present in the same web application. These will either be in a jar file within the WEB-INF/lib directory or as individual class files under the WEB-INF/classes directory.

TCP Server Usage

For TCP, JiBX/WS provides a TcpServer class.

Each service running on the TcpServer must run on a separate port and be specified as a command-line argument. Each command-line argument is of the format def-path=port#, where def-path is the path to the service definition file and port# is the corresponding service port number.

In addition to the runtime dependencies, the actual service implementation classes must also be present on the classpath.