Creating a service mock for 3d party soap service

[FrankZeTank]

Hello everyone,

I was tasked with creating a service mock for a SOAP service provided by a 3rd party (government).
I know a little SOAP but am at a point where I am lost.

Naturally, seeing as I enjoy using Quarkus and it had an extension for CXF I thought it would be a effective way to get the job done.

I was only able to create the classes with WSDL2java as someone had the bright idea to move some of the locations to https and needed a catalogue to solve it.
The WSDL contains one service 'TheService' with three ports & bindings which become three WebServices. The WebServiceClient also provides methods to get these.

I can also publish these sevices and use them with the CXFClient. No Problem.
I have interceptors that add-in special handlings and it works great.

The only 'problem' is that what I get on the interface of my mock is not the same as the one from the original.
As I have the three endpoints configured in my application.properties, I get the three resource paths and three wsdl files.

F.i. the WebServiceClient's constructor uses the service name 'TheService' and then gets the ports/actual services.

I have no idea how to combine them under one service. Or do I pass back the original wsdl for each endpoint?
Cloned the sources and tests but could not find anything obvious.

Now I know to little if this is a problem or if I am on a fools errand.
Just running out of time and motivation for more trial-and-error solution seeking.

Thanks!

[ppalaga]

what I get on the interface of my mock is not the same as the one from the original.
As I have the three endpoints configured in my application.properties, I get the three resource paths and three wsdl files.

I am not sure I understand what you mean. Could you please describe in more detail what does not meet your expectations?
Maybe showing what you have in your application.properties and Java files would help.

[FrankZeTank]

Hey pplaga,
thanks for the reply.

So basically we get a WSDL file from our customer that looks kinda like this:

<wsdl:service name="Lighting">
    <wsdl:port name="SwitchPower" binding="tns:SwitchPower">
        <soap:address location="INSERT_YOUR_URL_HERE" />
    </wsdl:port>
    <wsdl:port name="Dimming" binding="tns:Dimming">
        <soap:address location="INSERT_YOUR_URL_HERE" />
    </wsdl:port>
</wsdl:service>

Now I have to create a mock impl that itself provides a WSDL matching the above signature (naturally with the locations fixed).
I have the services

@WebService
(
    serviceName = "Lighting",
    portName = "SwitchPower",
..

But It seems that if I define the endpoints in the application.properties

quarkus.cxf.endpoint."/SwitchPower".implementor = my.code.SwitchPowerImpl
quarkus.cxf.endpoint."/Dimming".implementor = my.code.DimmingImpl

I get three services with each one endpoint.
I also tried using the 'quarkus.cxf.java2ws.includes' but that seems to be redundant to the above.

Now I have managed to work around it by creating a WebService that provides a manipulated version of the original WSDL.
But I it would be nice if the plugin could do that as well.

Thanks and best regards

[ppalaga]

Thanks for the explanation, @FrankZeTank.

The missing service abstraction that would allow to group multiple @WebService implementations seems to be a limitation of CXF itself and it would be better to fix it there rather than here in Quarkus CXF. You may want to file a new issue.

The only workaround seems to be what you already did: setting a local/edited WSDL document on the service endpoints either using quarkus.cxf.endpoint."/endpoint-path".wsdl or via @WebService(..., wsdlLocation = "classpath:wsdllocation/HelloService.wsdl").
There is an open issue https://issues.apache.org/jira/browse/CXF-7398 that asks for those non-current ports to have the addresses set properly. You may want to upvote that one if it would make your life easier.