Which version of XFire are you using? The setConfiguration method was
introduced at March 21st, so it is in 1.1.
If you are using 1.1, can you make sure you haven't any older version on
you classpath?
Mika
Kerzhner, Olia schrieb:
Figured out the first part of the problem -- the url suggested in the example
wasn't correct, didn't match the actual app name.
Now I'm getting an exception:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'org.codehaus.xfire.spring.ServiceBean' defined in class path
resource [META-INF/xfire/services.xml]: Initialization of bean failed; nested
exception is java.lang.NoSuchMethodError:
org.codehaus.xfire.aegis.type.java5.Java5TypeCreator.getConfiguration()Lorg/codehaus/xfire/aegis/type/Configuration;
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:370)
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:226)
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:147)
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:275)
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:320)
org.codehaus.xfire.spring.XFireConfigLoader.getXFireApplicationContext(XFireConfigLoader.java:102)
org.codehaus.xfire.spring.XFireConfigLoader.loadContext(XFireConfigLoader.java:38)
org.codehaus.xfire.transport.http.XFireConfigurableServlet.loadConfig(XFireConfigurableServlet.java:75)
org.codehaus.xfire.transport.http.XFireConfigurableServlet.createXFire(XFireConfigurableServlet.java:51)
org.codehaus.xfire.transport.http.XFireServlet.init(XFireServlet.java:43)
javax.servlet.GenericServlet.init(GenericServlet.java:211)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
java.lang.Thread.run(Thread.java:595)
This is till the plain old "book" example. Any advice?
-----Original Message-----
From: Kerzhner, Olia [mailto:[EMAIL PROTECTED]
Sent: Friday, May 12, 2006 10:43 AM
To: [email protected]
Subject: RE: [xfire-user] Generating a WSDL from service code?
HTTP Status 404 - /book/services/BookService.wsdl
--------------------------------------------------------------------------------
type Status report
message /book/services/BookService.wsdl
description The requested resource (/book/services/BookService.wsdl) is not
available.
--------------------------------------------------------------------------------
Apache Tomcat/5.5.9
The file is just not there, it wasn't in my build directories (under "target"),
nor under the servlet installation. Should it have been genereated during maven build?
I couldn't find anything there.
-----Original Message-----
From: Tomek Sztelak [mailto:[EMAIL PROTECTED]
Sent: Friday, May 12, 2006 12:29 AM
To: [email protected]
Subject: Re: [xfire-user] Generating a WSDL from service code?
wsdl should be there. What error message did you get ? Is anything interesting
in server logs ?
On 5/12/06, Kerzhner, Olia <[EMAIL PROTECTED]> wrote:
Hi,
Could someone point me to the directions on how to generate a wsdl
file from my service code?
I built/installed book example, and its README claims:
The WSDL file for the service should be viewable at:
http://yourhost:port/book/services/BookService?wsdl
But it ain't... How was it supposed to have been generated?
Thanks in advance!
Olia
--
Your plan looks like it was written by a drunken lemur as a practical joke on
other drunken lemurs.
-----
Fight back spam! Download the Blue Frog.
http://www.bluesecurity.com/register/s?user=dG9tZWtz
--
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]