The WSDL has the standard WSN WSDL content, so I doubt its invalid WSDL content... how does soapUI make the request? Do you have a chance to enter values for the parameters in the request? Subscribe() has a number of parameters, so I'd be interested to know what values you provided and whether soapUI seems to be ignoring them or not.
Dan "Ramesh Gurunathan" <[EMAIL PROTECTED]> wrote on 12/08/2006 05:04:37 AM: > Hi, > > My application clients are non-java applications and so they can't use > muse API for notification subscription requests. They truly rely on > SOAP for communication with the notification server. WSDL is the only > contract between the (notification) server and the clients. > > So I decided to generate a sample SOAP message for Topic subscription. > This will give a heads-up to the application client developers. > > I tried to load the WsResource.wsdl file of wsn-producer sample in the > XML Spy editor, it crashed. I thought it could be due to a bug in XML > Spy, then I decided to load it in SOAP UI (1.6 final) tool, it > successfully loaded the wsdl and all it's import files, but when > generating a SOAP request for 'Subscribe' operation, it only produced > an empty soap request. > > Any ideas what could be wrong? Is there anything wrong in the WSDL? > > Appreciate your advice. > > Ramesh > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
