cloudfoundry-client | Ruby wrapper for the CloudFoundry API | Continuous Deployment library

Solution: CF Java Client v2 has a different API from v1, so you won't find CloudCredentials in v2. See the v2 README for examples of constructing a new client and providing credentials: https://github.com/cloudfoundry/cf-java-client#cloudfoundryclient-dopplerclient-uaaclient-builders Again, use only the v2 libraries and don't use any v1 libraries in the same app.

I'm not sure exactly where that error is coming from, but you are mixing different major versions of the CF Java client in the same app. That's not likely to work very well. Refer to the project page for the CF Java Client and use only 2.x.x versions of all the org.cloudfoundry dependencies. All of the org.cloudfoundry dependencies should also be on the same versions.

So replace:

Apparently, you are missing this reactor-core dependency:

io.projectreactor reactor-core ${reactor.version}

Choose the compatible version for the reactor core. For instance, if you are using CF deployer 1.2.x then choose any of the 3.0.x versions of reactor-core.

The CF Java libraries communicate with Cloud Controller, not with service brokers directly. The CC API documentation specifies the contract between CC and a client (i.e. your app using the CF Java libraries). The service broker API documentation specifies the contract between CC and a service broker.

I changed the implementation of my custom service broker to provide some data in the response to the bind request

What data are you providing in the response? As stated in the service broker API docs, only the listed fields are recognized by CC and all other fields will be ignored. The fields that are listed in the docs are stored internally by CC, not necessarily returned in response to the CC API call. So you can't expect arbitrary fields in your broker's bind response to make it back to a CC API client (Java library or otherwise).

Any data from a service broker that you want to be a available to a CC API client should be added to the credentials field of the broker's bind request. That field is returned all the way out to the CC API client, and is the typical way that bound apps consume bindings.