Forum Discussion

glTranter's avatar
glTranter
New Contributor
13 years ago

maven-soapui-plugin (4.0.0) not shutting down correctly

I am having problems with missing operation errors in a maven multi module project.

I have three webservices, each in its own multi module project, which defines the interface and the implementation. service1 calls service2, service1 and service2 all call service3.
Service1 and Service2 are further housed in another multi module project that contains some common elements. due to their ordering service2 builds before service1 in the main multi module project.

However when I run mvn clean install from the main multi module project the soapUI plugin for Service1 integration tests fails reporting missing operation. Just to be clear this would be the second failsafe run and thus the second usage of soapui.

When I mvn clean install for Service1 on its own, it all works fine, the only thing that has changed is the directory from which I am running mvn.

The missing operation is in the mockService as it is the last thing I have added to the soapUI file.

I am using:
Ubuntu
maven 3
Java 1.6
SoapUI 4 to create the mocks
maven-soapui-plugin 4.0.0

Any help would be great

Thanks
Gavin
  • glTranter's avatar
    glTranter
    New Contributor
    13 years ago
    I am now of the opinion that this is a bug within the soapUI plugin.

    The plugin is run for the int testing of the service2, but doenst shut down when that round of int testing has finished, it is then started again for service1 when service1 makes calls to service2 it looks like these are mocked correctly. However when service2 makes calls to the common service3 it looks like the calls are routed to the mock created for service1.

    This is shown by the fact that the mocks for service2 do not contain the same end points as for service1, and both mocks use different port numbers for the mocking of service3. when the missing end points are added to service2 mock all tests pass.

    The defect is either that the soapUI plugin is unable to shut itself down after the end of the build phase for service2, or that soapUI's internal routing is unable/fails to determin the correct mock based upon the port address.
    Of course I could be missing a configuration option.

    Is there a way to stop/shutdown/kill the soapUI plugin at the end of the build cycle so that when the pom is activated for service1 there is no soapUI run?