Forum Discussion

jtheuer's avatar
jtheuer
Occasional Contributor
16 years ago

Service enpoint: path is removed

Hi, according to http://www.soapui.org/userguide/interfa ... oints.html I added a new endpoint: https://myserver.tld:8712/mycontextpath/ . Using the endpoint in TestCases, I noticed in the RAW view of the request that "mycontextpath" is removed and the service base path is directly appended, like this:
https://myserver.tld:8712/service/people/?name=...

Is it a known bug? Is it fixed in the current Beta? i still use 3.0.1

Jan

2 Replies

  • jtheuer's avatar
    jtheuer
    Occasional Contributor
    16 years ago
    same for the maven integration tests: any trailing path from the endpoint is removed.

    How can I define a path between the service endpoint definition and the REST url?
  • jtheuer's avatar
    jtheuer
    Occasional Contributor
    16 years ago
    Hi, I just applied for the PRO version, but it doesn't seem to solve my problem. I have several service enpoints: http://localhist:8080/, https://testserver.company.tld/release/47/, ... and I want to be able to (1) run the test inside SoapUI (2) automatically run maven by maven.

    I tried to add the path to the service enpoints, as I wrote, paths are ignored (for some unknown reason without any notice, ...)

    I tried to add a project parameter ${#Project#endpoint-path} which allows me to dynamically set the enpoint in my project (GREAT!). However in maven, setting

    <configuration>
         <testSuite>UseCases</testSuite>
         <endpoint>https://testserver:8999/</endpoint>
         <projectProperties>
          <endpoint-path>/release/47</endpoint-path>
         </projectProperties>
         <printReport>true</printReport>
         <saveAfterRun>false</saveAfterRun>
         </configuration>

    does not overwrite it.

    Do you have any other Ideas?

    Cheers,

    Jan