Hello,

 

I am developing a WSDL-first XFire service using the XFireExporter with
Spring Remoting.  Although I want my WSDL to mainly remain as written, I
would like XFire to dynamically modify the service URL portion
(<soap:address location="http://localhost:8080/myapp/MyService"/>) to
match the server and port it is running on.

 

XFire already does this for java-first deployments, but doesn't appear
to do it with WSDL-first deployments.  Digging through some code, I've
discovered the main difference:  WSDL-first deployments use the
ResourceWSDL implementation of WSDLWriter.  This just copies the WSDL
byte-for-byte.  Java-first implementations use the WSDLBuilder
implementation of WSDLWriter-this generates the WSDL on-the-fly and
through a series of calls, eventually calls down to
XFireServletTransport.getServiceURL(...), which dynamically generates
the correct URL based on server name and port.

 

Has anyone discovered a way to accomplish this in WSDL-first
development?  This service will be deployed on multiple servers in
multiple infrastructures, and I'd rather not have to modify the physical
WSDL file for each separate installation.

 

Thanks!

 

-Chris

Reply via email to