Re: [Soaplab-users] Soaplab2, WSDLs and third-party clients

[Andrew C. <cl...@bi...>]

On Thursday 05 June 2008 17:14, Mahmut Uludag wrote:
>
> if I look at how jaxws replaces the same string in the dynamic wsdl it
> generates
>
> http://localhost:8080/soaplab2/services/list?wsdl
>
> i found it is replaced by "http://localhost:8080/soaplab2/services/list"
>
> you may try appending "/list" to your replacement url

Okay, that works for AnalysisList.wsdl, thanks. Not really sure what I'm doing 
with Analysis.wsdl though, to be honest.

If I put the name of a specific service in there 
(e.g. /soaplab2/services/helloworld) I get "unknown service 'helloworld'".

This is despite the fact that I haven't changed any defaults, and my web.xml 
in Tomcat says:

  <!-- Soaplab2 all other services -->
  <servlet-mapping>
    <servlet-name>soaplab2</servlet-name>
    <url-pattern>/services/*</url-pattern>
  </servlet-mapping>

which suggests to me that /soaplab2/services/helloworld should work.

(These are just calling the describe method, nothing with parameters yet.)

Am I missing something? Do I need to do something else to let Tomcat or 
Soaplab know which URLs relate to which services?

Thanks again,

Andrew.