From e74a86cd9e23cee45fdbdab9003fd153e35c46ea Mon Sep 17 00:00:00 2001 From: Chris Beams Date: Tue, 10 Aug 2010 23:10:35 +0000 Subject: [PATCH] Remove XFire reference documentation (SPR-7434) XFire is now CXF (per http://xfire.codehaus.org), and given that Spring does not actually ship with any explicit XFire support, it makes sense to remove the documentation completely. CXF does provide support for writing services with Spring, and they provide their own documentation. See http://cxf.apache.org/docs/writing-a-service-with-spring.html git-svn-id: https://src.springframework.org/svn/spring-framework/trunk@3561 50f2f4bb-b051-0410-bef5-90022cba6387 --- spring-framework-reference/src/remoting.xml | 63 +-------------------- 1 file changed, 1 insertion(+), 62 deletions(-) diff --git a/spring-framework-reference/src/remoting.xml b/spring-framework-reference/src/remoting.xml index 9858afbd32d..70f5306f041 100644 --- a/spring-framework-reference/src/remoting.xml +++ b/spring-framework-reference/src/remoting.xml @@ -536,10 +536,7 @@ public class AccountServiceImpl implements AccountService { url="http://www.springframework.org/spring-ws">Spring Web Services, a solution for contract-first, document-driven web services - highly recommended for building modern, future-proof web - services. Last but not least, XFire also allows you to export - Spring-managed beans as a web service, through built-in Spring - support. + services.
Exposing servlet-based web services using JAX-RPC @@ -995,64 +992,6 @@ public class AccountServiceEndpoint { JAX-WS endpoint artifacts; you need to annotate them accordingly first. Check the JAX-WS documentation for details on those requirements.
- -
- Exposing web services using XFire - - XFire is a lightweight SOAP library, hosted by Codehaus. Exposing - XFire is done using a XFire context that is shipping with XFire itself in - combination with a RemoteExporter-style bean you have to add to your - WebApplicationContext. As with all - methods that allow you to expose service, you have to create a - DispatcherServlet with a corresponding - WebApplicationContext containing the - services you will be exposing: - - <servlet> - <servlet-name>xfire</servlet-name> - <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class> -</servlet> - - You also have to link in the XFire configuration. This is done by - adding a context file to the contextConfigLocations - context parameter picked up by the - ContextLoaderListener (or - ContextLoaderServlet for that matter). - - <context-param> - <param-name>contextConfigLocation</param-name> - <param-value>classpath:org/codehaus/xfire/spring/xfire.xml</param-value> -</context-param> - -<listener> - <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> -</listener> - - After you added a servlet mapping (mapping /* - to the XFire servlet declared above) you only have to add one extra bean - to expose the service using XFire. Add for example the following - configuration in your 'xfire-servlet.xml' - file: - - <beans> - - <bean name="/Echo" class="org.codehaus.xfire.spring.remoting.XFireExporter"> - <property name="serviceInterface" value="org.codehaus.xfire.spring.Echo"/> - <property name="serviceBean"> - <bean class="org.codehaus.xfire.spring.EchoImpl"/> - </property> - <!-- the XFire bean is defined in the xfire.xml file --> - <property name="xfire" ref="xfire"/> - </bean> - -</beans> - - XFire handles the rest. It introspects your service interface and - generates a WSDL from it. Parts of this documentation have been taken - from the XFire site; for more detailed information on XFire Spring - integration, navigate to http://docs.codehaus.org/display/XFIRE/Spring. -