Codehaus XFire

Documentation

Quicklinks

Developers

Sponsors

If you are just using the XFire API (as opposed to the configuration support which is provided via Spring), you will still need to set up the XFire servlet to expose services over HTTP(S). Below is a sample web.xml:

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
    
<web-app>

  <servlet>
    <servlet-name>XFire</servlet-name>
    <display-name>XFire Servlet</display-name>
    <servlet-class>
        org.codehaus.xfire.transport.http.XFireConfigurableServlet
    </servlet-class>
    <!-- override default location of config file with the config param -->
    <init-param>
      <param-name>config</param-name>
      <param-value>services.xml</param-value>
    </init-param>
  </servlet>

  <servlet-mapping>
    <servlet-name>XFire</servlet-name>
    <url-pattern>/servlet/XFireServlet/*</url-pattern>
  </servlet-mapping>

  <servlet-mapping>
    <servlet-name>XFire</servlet-name>
    <url-pattern>/services/*</url-pattern>
  </servlet-mapping>
  
</web-app>

The above mapping makes services available at http://host:port/CONTEXT/services/NAME, where host, port, CONTEXT, and NAME are dependent on your local installation. One example might be http://localhost:8080/xfire/services/WeatherService.

The wsdl file can be viewed by appending "?wsdl" for instance "http://localhost:8080/xfire/services/WeatherService?wsdl".