Pivotal Cloud Foundry Plus MySql DB答案

【问题标题】：Pivotal Cloud Foundry Plus MySql DBPivotal Cloud Foundry Plus MySql DB
【发布时间】：2018-05-25 19:23:59
【问题描述】：

我在 Pivotal Cloud Foundry 上有一个正在运行的 Web 服务应用程序。
我添加了一项服务，即 MySql DB，并将其与 Web 服务应用程序绑定。
我的问题是如何在 (Spring-boot) 中使用 Java API Plus Cloud Foundry API 获取 My Sql db 的数据源。

我尝试过的事情：

 public class Configuration {
        @Configuration
        @Profile("cloud")
        static class CloudConfiguration {
            @Bean
            public DataSource dataSource() {
                CloudFactory cloudFactory = new CloudFactory();
                Cloud cloud = cloudFactory.getCloud();
                String serviceID = cloud.getServiceID();
                return cloud.getServiceConnector(serviceID, DataSource.class, null);
            }
 }

方法执行：

Configuration.CloudConfiguration cloudConfiguration = new CloudConfiguration();
        cloudConfiguration.dataSource();

我得到的错误：

我从这段代码中得到 CloudException，就像找不到合适的 CloudConnector，getCloud() 方法会抛出 CloudException。

清单文件详细信息：

applications:
    - name: springboot-cloudfoundry
      memory: 512M
      instances: 1
      path: target/springboot-cloudfoundry-0.0.1-SNAPSHOT.jar
      buildpack: https://github.com/cloudfoundry/java-buildpack
      env:
        SPRING_PROFILES_ACTIVE : cloud

    POM File:
        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-spring-service-connector</artifactId>

        </dependency>
        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-cloudfoundry-connector</artifactId>

        </dependency>

Stack Trace:
org.springframework.cloud.CloudException: No suitable cloud connector found
    at org.springframework.cloud.CloudFactory.getCloud(CloudFactory.java:55)
    at org.springframework.cloud.config.CloudScanHelper.initializeCloud(CloudScanHelper.java:85)
    at org.springframework.cloud.config.CloudScanHelper.registerServiceBeans(CloudScanHelper.java:55)
    at org.springframework.cloud.config.java.ServiceScanConfiguration.registerBeanDefinitions(ServiceScanConfiguration.java:22)
    at org.springframework.cloud.config.java.CloudScanConfiguration.registerBeanDefinitions(CloudScanConfiguration.java:22)
    at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsFromRegistrars(ConfigurationClassBeanDefinitionReader.java:344)
    at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:151)
    at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:124)
    at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:318)
    at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:88)
    at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$3.run(BeansJavaConfig.java:328)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.executePostProcessor(BeansJavaConfig.java:321)
    at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.access$5(BeansJavaConfig.java:319)
    at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:233)
    at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:1)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

【问题讨论】：

no suitable CloudConnector is found 消息通常意味着 Spring Cloud Connector 代码看不到 VCAP_APPLICATION 和 VCAP_SERVICES 环境变量。 getCloud() method throws a CloudException 消息不寻常。该异常是否有堆栈跟踪？
堆栈跟踪已更新。
如何设置这些变量 VCAP_APPLICATION 和 VCAP_SERVICES 我想从云中获取它，就像我们从 CLI 命令中获取它一样。有没有办法做到这一点，我不想把它们放在属性文件中，
当应用在 CF 上运行时，这两个 env vars 应该被自动设置。如果您尝试以与在 CF 上运行相同的方式在本地测试应用程序，则需要在应用程序环境中手动设置它们。
你用的是什么 CF 风格？ Pivotal Cloud Foundry、Blue Mix、SAP、Suse、OSS？

标签： spring-boot cloud-foundry pivotal-web-services

【解决方案1】：

1 将以下依赖项添加到您的 pom.xml 中

    <dependency>
        <groupId>io.pivotal.spring.cloud</groupId>
        <artifactId>spring-cloud-services-starter-config-client</artifactId>
    </dependency>

或

<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-spring-service-connector</artifactId>
    <version>1.2.3.RELEASE</version>
</dependency>
<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-cloudfoundry-connector</artifactId>
    <version>1.2.3.RELEASE</version>
</dependency>

2 定义数据源：

public class CloudConfig extends AbstractCloudConfig {
        @Bean
        public DataSource dataSource() {
            DataSource dataSource = connectionFactory().dataSource();
            return dataSource;
        }
}

或

public class CloudConfig extends AbstractCloudConfig {
        @Bean
        public DataSource inventoryDataSource() {
            return connectionFactory().dataSource("mysql-db-service");
        }
}

【讨论】：