Tom van den Berge wrote:
Hi,
Thanks for your response. I'm not using maven2, and I'm also not
familiar with it. That's probably why I don't understand your response.
Can you please give me some clues?
Does this mean I need to (re)build xfire? Which pom file are you
referring to? How do I do this?
I'm completely lost on the 'spring remoting' functionality. Do I need
this, and why?
Since your not using maven you can just skip that part. The important
thing is to not have both spring-1.2 jar and spring-2.0 jar in your
application classpath.
The spring remote functionality is about the way to expose services. You
basically just following the instructions at
http://xfire.codehaus.org/Spring+Remoting. Short version is the stuff i
wrote in my last post. You have to create a url that xfire will handle
e.g. /services/* and then create regular bean definitions in
/WEB-INF/xfire-servlet.xml like this (from the referred url):
<bean
class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
<property name="urlMap">
<map>
<entry key="/EchoService">
<ref bean="echo"/>
</entry>
</map>
</property>
</bean>
<!-- Declare a parent bean with all properties common to both services -->
<bean id="echo" class="org.codehaus.xfire.spring.remoting.XFireExporter">
<property name="serviceFactory">
<ref bean="xfire.serviceFactory"/>
</property>
<property name="xfire">
<ref bean="xfire"/>
</property>
<property name="serviceBean">
<ref bean="echoBean"/>
</property>
<property name="serviceClass">
<value>org.codehaus.xfire.spring.example.Echo</value>
</property>
</bean>
This connects the url /EchoService with the "echo"-bean. The Echo bean
is of the type XFireExporter and takes several arguments like the
ServiceBean that refers to the service interface and serviceClass which
is the implementation class.
--
Henning Jensen
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
