XFire

services.xml file not being found when war file is not expanded

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.2.3
  • Fix Version/s: 1.2.6
  • Component/s: Core
  • Labels:
    None
  • Environment:
    Windows XP server running tomcat 5.5.17
  • Number of attachments :
    0

Description

XFireConfigurableServlet does not seem to be able to read the services.xml file from a non expanded war file. As soon as I expand the war file everything runs as expected.
I have the services.xml file place in WEB-INF/META-INF/xfire/services.xml. My web.xml file looks like the following. Notice I am not specifying where the services.xml file is located. Although that does not seem to matter either way.

<servlet>
<servlet-name>XFire</servlet-name>
<display-name>XFire Servlet</display-name>
<servlet-class>org.codehaus.xfire.transport.http.XFireConfigurableServlet</servlet-class>
</servlet>

<servlet-mapping>
<servlet-name>XFire</servlet-name>
<url-pattern>/xfire/*</url-pattern>
</servlet-mapping>

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dan Diephouse added a comment -

Thanks for filing this. Scheduling for the 1.2.5 release.

Show
Dan Diephouse added a comment - Thanks for filing this. Scheduling for the 1.2.5 release.
Hide
Permalink
Tomasz Sztelak added a comment -

Can you tell how did you configured server ? I just run book example on tomcat 5.5.20 with

<Host name="localhost" appBase="webapps"
unpackWARs="false" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">

and everything works fine.

Show
Tomasz Sztelak added a comment - Can you tell how did you configured server ? I just run book example on tomcat 5.5.20 with <Host name="localhost" appBase="webapps" unpackWARs="false" autoDeploy="true" xmlValidation="false" xmlNamespaceAware="false"> and everything works fine.
Hide
Permalink
Dave Kallstrom added a comment -

I just tried this again and found out that if I specify the location of the services.xml file like the following
<servlet>
<servlet-name>XFire</servlet-name>
<display-name>XFire Servlet</display-name>
<servlet-class>org.codehaus.xfire.transport.http.XFireConfigurableServlet</servlet-class>
<init-param>
<param-name>config</param-name>
<param-value>services.xml</param-value>
</init-param>
</servlet>
and leave the war file packed the application correctly finds services.xml if it is in the classpath.
So in my case I placed the services.xml in WEB-INF/classes. However if I do not specify the location of the services.xml file xfire assumes it is in META-INF/xfire/services.xml
which would not typically be on the classpath. If you take a look at XFireConfigLoader you'll notice that when the file does not exists on disk it uses ClassPathResource to load the file.
So this may not be an issue with the code but may be an issue with the documentation for the location of services.xml.

Show
Dave Kallstrom added a comment - I just tried this again and found out that if I specify the location of the services.xml file like the following <servlet> <servlet-name>XFire</servlet-name> <display-name>XFire Servlet</display-name> <servlet-class>org.codehaus.xfire.transport.http.XFireConfigurableServlet</servlet-class> <init-param> <param-name>config</param-name> <param-value>services.xml</param-value> </init-param> </servlet> and leave the war file packed the application correctly finds services.xml if it is in the classpath. So in my case I placed the services.xml in WEB-INF/classes. However if I do not specify the location of the services.xml file xfire assumes it is in META-INF/xfire/services.xml which would not typically be on the classpath. If you take a look at XFireConfigLoader you'll notice that when the file does not exists on disk it uses ClassPathResource to load the file. So this may not be an issue with the code but may be an issue with the documentation for the location of services.xml.

People

  • Assignee:
    Tomasz Sztelak
    Reporter:
    Dave Kallstrom
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: