Well, I think import resolution would be a basic feature of such tools, but if your assumption is correct, try this:
1. Run wsdl2java on the WsResource.wsdl file. Remember to have the other files it imports in the same directory as the file. They are in /docs/2.0.0/specs. 2. Get the WSDL file from the generated project. It's in /WEB-INF/services/muse/wsdl/WsResource.wsdl. This file will have the same content, but all the imports will be resolved (consolidated into one file). 3. Try soapUI on the new WsResource.wsdl file. There should not be any imports in it, so if that's the issue, everything should work. Dan "Ramesh Gurunathan" <[EMAIL PROTECTED]> wrote on 12/08/2006 11:11:38 AM: > SOAPUI basically lists all the port type operations. I can choose the > operation I want to invoke. It will compose a SOAP message and places > '?' for all the mandatory/optional elements to allow user to enter > values. For the 'Subscribe' operation, it didn't show any SOAP message > at all. The input panel was empty. So I thought there must be > something wrong in the way WSDL defines the web service. When I tried > with XML Spy, it was even worse. It just crashed. > > I looked at the WSDL (WsResource.wsdl), it had several levels of > imports. Import within import. It may be technically correct, but > tools are not robust enough yet? > > On 12/8/06, Daniel Jemiolo <[EMAIL PROTECTED]> wrote: > > 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] > > > > > > --------------------------------------------------------------------- > 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]
