Eoghan: Yes, that seems to have done the trick!!! Thanks for all your patience and advice working through this setup with me!
What is weird is that the WSDL returned by the app-server had the right address but the WSDL deployed did not so I did not think that changing it would matter... Guess it does. :) Mike Barlotta Associate Booz | Allen | Hamilton -----Original Message----- From: Eoghan Glynn [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2008 5:30 AM To: [email protected] Subject: Re: WS-RM enabling in CXF Barlotta, Michael [USA] wrote: > Eoghan: > > When I request the WSDL from the appserver using this URL: > http://localhost:8080/rmdemo/greet?wsdl > > CXF seems to change the <soap:address> from > http://localhost:9000/SoapContext/GreeterPort > to the correct URL that serves up the service. > > Here is the service portion: > <wsdl:service name="GreeterService"> > <wsdl:port binding="tns:Greeter_SOAPBinding" name="GreeterPort"> > <soap:address location="http://localhost:8080/rmdemo/greet"/> > <wswa:UsingAddressing/> > </wsdl:port> > </wsdl:service> So "http://localhost:9000/SoapContext/GreeterPort"; is the URI specified in the WSDL, but "http://localhost:8080/rmdemo/greet"; is the "real" URI, in the sense of the address that the app server is actually listening on? These URIs should ideally match up. Can you modify the WSDL accrordingly? [snip] > PS: Does CXF support WS-RM 1.1/2007 or have future plans to do so. The project we are going to integrate with is planning on using this version. CXF currently supports WS-RM 1.0 (2005/02). I don't know of any plans to add support for 1.1 the medium term, but feel free to propose this as part of the "Ideas for 2.2" discussion[1]. Cheers, Eoghan [1] http://www.nabble.com/Ideas-for-2.2-td17985028.html ---------------------------- IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
