Thanks Adam, I tried that. It seems that there is something seriously broken with the way XFire loads the services.xml file. If the path you specified doesn't exist under /WEB-INF/classes then it refuses to find the file. For e.g. if you specified /WEB-INF/services.xml in the context param value, then the file will have to be at /WEB-INF/classes/WEB-INF/services.xml
For all other software (struts, spring etc.) the above is not a problem. It's a problem only with Xfire. Any insights? Thanks, Rahul -----Original Message----- From: Adam Kramer [mailto:[EMAIL PROTECTED] Sent: Monday, April 10, 2006 4:12 PM To: [email protected] Subject: Re: [xfire-user] easier deployment of services.xml Rahul Pilani wrote: > > Hi, > > I wanted to use Xfire as a webservice provider in an existing project. > However, the requirement that the services.xml be in the > /META-INF/xfire/ folder makes it hard for me to integrate, as it would > require a build file change, and a lot of my developers wont be happy. > Is there a shortcut to including the service.xml file? Is there a > place that you can specify where the service.xml file resides? I am > using Tomcat as my container, and the war file format for deployment. > > > If you can change your web.xml file you can override where XFireConfigurableServlet looks for the config file(s). See http://xfire.codehaus.org/XML+Configuration under the 'Update your web.xml file' heading. > Any help is appreciated. > > > Thanks, > > Rahul Pilani > Adam
