[ http://jira.codehaus.org/browse/XFIRE-175?page=all ]
Dan Diephouse closed XFIRE-175.
-------------------------------
Resolution: Won't Fix
I'm not sure that this should be the behavior. If you don't have a services.xml
you can just use the org.codehaus.xfire.transport.http.XFireServlet - as
opposed to the XFireConfigurableServlet. Marking as won't fix unless there are
a lot of complaints... :-)
> If services.xml doesn't exist, the world should move on
> -------------------------------------------------------
>
> Key: XFIRE-175
> URL: http://jira.codehaus.org/browse/XFIRE-175
> Project: XFire
> Issue Type: Bug
> Reporter: Dan Diephouse
> Assigned To: Dan Diephouse
> Fix For: 1.2.3
>
>
> If services.xml doesn't exist, the world should move on:
> org.springframework.beans.factory.BeanDefinitionStoreException: IOException
> parsing XML document from class path resource [META-INF/xfire/services.xml];
> nested exception is java.io.FileNotFoundException: class path resource
> [META-INF/xfire/services.xml] cannot be opened because it does not exist
> java.io.FileNotFoundException: class path resource
> [META-INF/xfire/services.xml] cannot be opened because it does not exist
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
