How handle a different label for Solace

[murillocg]

Hello,

I'm unsure if this is the right place to ask this question. If not, please let me know the right one.

At my company, we've been using the Cloundfoundry as PaaS, but the Solace service name is not solace-pubsub, so the library solace-java-cfenv does not work for me https://github.com/SolaceProducts/solace-spring-boot/tree/master/solace-java-cfenv.

I'm using this dependency in our Spring Boot applications, but it's not able to instantiate the SolaceJavaProperties and I need to do so on my side because of this issue.

<dependency>
	<groupId>com.solace.spring.boot</groupId>
	<artifactId>solace-java-spring-boot-starter</artifactId>
</dependency>

Best Regards

[Nephery]

Right now, solace-java-cfenv finds its services by looking for a solace-pubsub label or a solace-pubsub tag.

Sounds like we need to make the service lookup label (and maybe tag) configurable and expose that to Spring Boot auto-configuration. Maybe we can call them something like solace.cloudfoundry.service-lookup.label and solace.cloudfoundry.service-lookup.tag.

[murillocg]

It is worth mentioning that, beyond the service name, the properties are different as well. You can see it in our workaround using the application.properties here:

# Solace Properties
solace.java.host=${vcap.services.message-queuing.credentials.smf.url}
solace.java.msgVpn=${vcap.services.message-queuing.credentials.brokerName}
solace.java.clientUsername=${vcap.services.message-queuing.credentials.smf.auth.basic.userName}
solace.java.clientPassword=${vcap.services.message-queuing.credentials.smf.auth.basic.password}