Forum Discussion

guaguanco's avatar
guaguanco
New Contributor
16 years ago

Changing relative URLs for schema components?

I've successfully created a WAR file (myMockService.war)  and deployed it to a Tomcat server. However, if I attempt to use soapUI to access the mock service, I get errors as it tries to import the WSDL. These are due to the fact that there's an extra directory level when the WAR file is deployed (as is typical of deployed WAR files):

http://server:8080/myMockService/MyServiceSoap11?WSDL

includes references to things like:
schemaLocation="/MyServiceSoap11?WSDL&interface=MyServiceSoap11&part=ComplexTypes.xsd"

which *would* work if they pointed to the deployment location:

schemaLocation="/myMockService/MyServiceSoap11?WSDL&interface=MyServiceSoap11&part=ComplexTypes.xsd"

I could create a Tomcat rewrite rule, or hack the deployed files to add the extra path element, but it seems like something that could/should be handled through soapUI. Any pointers?

Thanks in advance.

4 Replies

  • bbelovic's avatar
    bbelovic
    16 years ago
    Any chance you found a solution to this? Or does anyone else have one? Preferably something more elegant than rewrite rules (mostly because it's not necessarily an option).

    It seems as if mockServiceEndpoint parameter set during WAR generation, and that apprears in web.xml, should do exactly this, but I have seen no effect. What is its purpose?
  • jnustud's avatar
    jnustud
    15 years ago
    I have exactly the same problem. There needs to be a fix for this.
  • patelm5's avatar
    patelm5
    14 years ago
    I also have this problem, seems the only solution offered at the moment is to deploy to root,
  • phoenixxx82's avatar
    phoenixxx82
    New Contributor
    13 years ago
    I have the same problem. Is there some workaround to deploy mock into non root context of Tomcat server?