Home > Products > JRun > Support > Web Services
Macromedia JRun Support Center - Web Services

Using JRun, you can publish existing Java code as a web service, or write new code specifically as a web service. You also can create object- and tag-based clients that can invoke methods on remote web services, even when those services reside on non-Java platforms, such as Microsoft .NET.

The JRun web services implementation is built on Apache Axis, the third generation of the Apache Software Foundation's Simple Object Access Protocol (SOAP) engine. Macromedia dedicates full-time engineers to work on the Axis project. These engineers leverage their Axis experience to provide JRun with a powerful web services engine that supports SOAP 1.1, Web Services Description Language (WSDL) 1.1, and additional productivity features including the following:

WSDL document generation
Client code generation based on WSDL documents
Automatic deployment of web services
A JavaServer Pages (JSP) custom tag library for invoking web services

Publishing a web service in JRun is as simple as adding a few lines to a deployment descriptor to declare a Java class or Enterprise JavaBean (EJB) as a web service and expose specific methods as web service operations. Alternatively, you can expose a simple Java source file as a web services by changing its file extension to jws and copying it into a web application.

The following figure shows a typical web services scenario in JRun. A service requestor—an application on a company's Intranet, a partner application on the Internet, or an application on- an end-user device—invokes an operation (method) on a web service using the SOAP protocol. The operation invocation is sent as an XML document embedded in an HTTP request. The web server receives the HTTP request and passes it to the JRun web services engine (Axis), which reads the XML-formatted operation invocation and invokes the appropriate method on the Java class or EJB that provides the business logic for the web service. Axis generates an HTTP response that embeds the result of the method invocation formatted as an XML document. The HTTP response is sent back to the service requestor.

To Table of Contents Forward to next document