Petals BC SOAP

If the service provider is not available when deploying a SOAP consume, you will not be able to get the service provider WSDL. How do you manage this use case ?

Good point, I didn't think of that, but I'm not sure to understand in which case this could happen: the wsdl is loaded from the JBI descriptor, if there is no WSDL defined in the JBI descriptor, it's not going to be added later… or is there some kind of mechanism that does that in the SOAP BC?

No, in my mind, for a BC SOAP consumer, the WSDL is loaded from its defined service provider. The WSDL is loaded from the JBI descriptor for a BC SOAP provider.

When you say BC SOAP Provider, you mean a JBI Consumes, right?

In this commit, it only covers JBI Consumes and the previous (and current code) was only loading the WSDL from the JBI descriptor.

Concerning Provides (not touched by this commit)… well the WSDL is also loaded from the JBI descriptor!

The difference is that it seems that it is an error (SU start fails) if the WSDL is missing for the Consumes, but it does not (warning logged) if the WSDL is missing for the Provides.

Is there something wrong with all of that? Should we add functionality for loading the WSDL from the external SOAP provider (so for the JBI Provides)?

So I checked and for a BC SOAP Consumes (as declared in the JBI), the WSDL is JBI Service Provider's, and it is retrieved from the Petals Registry.

It wasn't clear before to me and it does mean there is a problem if there is no provider deployed on the Bus yet...

I will investigate that to fix it properly.

Ok, I reintroduced the loading of the WSDL on the first call when needed (I call that "on-demand"), I added an integration test (r37687) for it, but the WSDL is loaded earlier if possible.

Also, now it should work better than before for the on-demand behaviour because it's done in a much cleaner way and at the correct time (which wasn't the case before).