So you want to have a different URL for the WSDL and a different one for the service. You can do that but you might need to go underneath the good and tweak how XFire processes HTTP requests. You'll need to replace the XFireServletController with your own implementation by extending some of the methods in it. Go here to see how you can create a CustomXFireServletController:
http://arsenalist.com/2007/03/01/web-service-versioning-with-endpoints-using-xfire/ Once you do that, you can make your URLs map to anything you want by overriding methods like doService(..) etc. On 3/13/07, Andres Bernasconi <[EMAIL PROTECTED]> wrote:
Hi everyone, I am having some problems related to the XFIRE-832 issue. I was wondering if there was any way to add security to web services invocations only and not when clients want to see the WSDL (Since the ?WSDL is a query string the address for getting the WSDL and for posting messages is the same. ) Can I publish de WSDL in another address? (but that address should NOT handle web service requests) ¿?. Or is there any way to make the client avoid calling the WSDL when it is created with configuration (of course, it is an XFire client). Can you think of any other solution that does not involve modifying XFire's code? If not, I will modify XFire's code and post a "possible" solution. Please respond as this is becoming quite a problem to my team. Thanks a lot! Regards Andres B.
--------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
