Dave, Sounds like you had a bad day in the office... hopefully we can get you going today.
With regard to a tutorial - In defence of Dan (and the others) I found this about as simple to follow as any and got me started with an echo service in about 3 minutes http://xfire.codehaus.org/Quick+Start. I have a couple months knowledge on spring though so perhaps this helped... I'm going to try to help: "but when deploying it complains about not finding a bean named xfire" Please change web.xml to include the spring configuration (application context) files for xfire like so (it's in the xfire jar, and needs to be read for the spring beans factory): <web-app> <!-- For xfire context initialisation in a spring environment --> <context-param> <param-name>contextConfigLocation</param-name> <param-value>classpath*:org/codehaus/xfire/spring/xfire.xml</param-value> </context-param> <!-- Register the spring context listener --> <listener> <listener-class> org.springframework.web.context.ContextLoaderListener</listener-class> </listener> <servlet> <servlet-name>XFireServlet</servlet-name> <display-name>XFire Servlet</display-name> <servlet-class>org.codehaus.xfire.spring.XFireSpringServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>XFireServlet</servlet-name> <url-pattern>/servlet/XFireServlet/*</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>XFireServlet</servlet-name> <url-pattern>/services/*</url-pattern> </servlet-mapping> </web-app> >From the info you have given, I think that "might" be enough to get you going. I can't answer your other questions so well as I just WAR it up and put it on the server... If you put it on a server it's just for you, something like: http://YOUR_SERVER:PORT/WEB_APP/services/echo?wsdl I use it all in a spring config and wire it all up differently to you (SimpleUrlHandlerMapping to point to different services) but will be happy to send my files and help you get going... just post to the list and I'll do a skeleton app, configured the way I do it. Cheers Tim -----Original Message----- From: davewible [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 05, 2006 3:47 AM To: [email protected] Subject: Re: [xfire-user] Problems with Spring Good evening. Matt's site helps some but I think what is simple ought to be simple and I truly believe it to be with xfire. What doesn't help with the reply is ignoring the request. The raible link is a hushpuppy of sorts. I'm a fan of the people who've created xfire so any pub is good pub and I'm glad the link exists. <watch the wrap on he link below> http://netzooid.com/presentations/SOAWithXFire.ppt#271,20,Easy client Here's a question. If I use the XFireHttpServer class, server.start(); How do i know when I create my client where the endpoint is? the server is using jetty on machine A. How do I connect from machine B? What machine from the client's point of view and how do i know that? >From my view as a commodity Java coder I can tell you that WS were important 3-4 yrs ago. Now we have SOA, choreography, BPEL, etc and they are back. OK, they never went away but still... For the common coder, admitted here again, who hasn't been working on SOAP or WS for the last yr or 2yrs + getting xfire (or any web service besides axis from 3-4 yrs ago ) working is new. Remember there's other 'stuff' like Spring, Hibernate, app servers, java 5, java 6 not including the xml technologies that have been our focus. Not including evolving architectures plus RoR and God save your soul Maven!! Enought of the sob story. The gift you can give to the Java community, which the Spring guys did a great job of, would be the 'put your nose in it' example(s) on Tomcat! I swear it won't take that long to do and I'd even be the guinea pig and I'll document the whole darn thing. If you do a search on Spring MVC step by step that things rocks. From the ANT build to the navigation it freakin' works with only minor tweaks that even I was able to figure out. Since 2003 they've updated it for Spring 2. >From there one can start to experiment which is what I did. I'll have some questions, from work, tomorrow morning, about the xfire example as well. Not the one from Dan's presentation but the service deployed on tomcat. If you would answer the question in here about the jetty example I'd appreciate it. I do not write this to emotionally complain or admonish you. You are donating your time and it is appreciated it's just people want to be able to get in the pool and at least consume the stuff. :-) Thanks for your time, David ----- Original Message ----- From: "Mika Göckel" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, April 04, 2006 3:27 PM Subject: Re: [xfire-user] Problems with Spring > Hey, > > maybe this helps: > > http://raibledesigns.com/wiki/Wiki.jsp?page=AppFuseXFire > > The simplest way to get the xfire def's into your Spring config is to > import it: > > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" > "http://www.springframework.org/dtd/spring-beans.dtd";> > > <beans> > > <import resource="classpath:org/codehaus/xfire/spring/xfire.xml"/> > <-------------------- > > <bean name="echoService" class="org.codehaus.xfire.spring.ServiceBean"> > <property name="serviceBean" ref="echo"/> > <property name="serviceClass" > value="org.codehaus.xfire.test.Echo"/> > <property name="inHandlers"> > <list> > <ref bean="addressingHandler"/> > </list> > </property> > </bean> > > > > Vinicius Carvalho schrieb: >> Hello! I'm trying to get XFire working using SpringServiceBean. Well I'm >> very frustated as the site is totally incomplete, following the steps on >> the site results on errors. Here's what I've done so far: >> >> bean name="echoService" class="org.codehaus.xfire.spring.ServiceBean"> >> <property name= >> "serviceBean" ref="echo"/> >> <property name="serviceClass" >> value="org.codehaus.xfire.test.Echo"/> >> <property name="inHandlers"> >> <list> >> <ref bean="addressingHandler"/> >> </list> >> </property> >> </bean> >> >> <bean id="echo" class="org.codehaus.xfire.test.EchoImpl >> "/> >> >> <bean id="addressingHandler" >> class="org.codehaus.xfire.addressing.AddressingInHandler" >> /> >> >> <web-app> >> <servlet> >> <servlet-name>XFireServlet</servlet-name> >> >> <display-name>XFire Servlet</display-name> >> <servlet-class> >> org.codehaus.xfire.spring.XFireSpringServlet >> >> </servlet-class> >> </servlet> >> >> <servlet-mapping> >> <servlet-name> >> XFireServlet</servlet-name> >> <url-pattern>/servlet/XFireServlet/*</url-pattern> >> </servlet-mapping> >> >> <servlet-mapping> >> <servlet-name>XFireServlet</servlet-name> >> <url-pattern>/services/*</url-pattern> >> </servlet-mapping> >> </web-app> >> >> I've replaced the echobean for one of my beans, but when deploying it >> complains about not finding a bean named xfire. So I've tried the site >> and there's no mention of it. So I've opened the XFireSpringServlet class >> source and found that it looks for a xfire bean. I've tried to configure >> it, but as theres no documentation on it, it's kinda hard, I've lost a >> couple of hours trying to get this to work, it's very frustating. Could >> someone point the right direction. And after I get this working I'd like >> to contribute to the site (if anyone else could) I think this lack of >> documentation a major flaw on the project. >> >> Regards > > > -- > cyber:con gmbh > Mika Göckel > > Rathausallee 10 > 53757 Sankt Augustin > > tel (+49)2241 / 9350 0 > fax (+49)2241 / 9350 99 > mob (+49) 172 / 279 2771 > skype mika.goeckel > email [EMAIL PROTECTED] > >
