Thanks Chris. I did this myself today as well and was going to post it but ran out of time. Yes, it is a much clean approach to the problem. One thing that keeps sticking in my head though is the location of the xfire schema. (services.xsd)
I've modified my root element in services.xml file as follows: <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xf="http://xfire.codehaus.org/config/1.0"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://xfire.codehaus.org/config/1.0 services.xsd"> As you can see from the last line I am attempting to specify the location of the schema. This is useful when editing the file in the Eclipse Studio or XML Spy as advanced editors can provide you with the correct avaialable elements for the editing location in the document. I know this is trivial but I think if it is possible to reference a publicly published xsd there would be far fewer configuration problems for all. Of course the above example does not work as there is no way for the editor to load services.xsd from the classpath with this specification. If the schema was published, for example, at the location: http://xfire.codehaus.org/config/1.0/services.xsd the it would be very simple for everyone to utilize this type of syntax. Thanks for the help.... --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
