Java 无法获取Mule ESB-Studio工件

我正在尝试在Mule Studio 3.4中测试数据库连接。我不断收到错误，并在错误日志中不断注意到这一特定错误。这是想告诉我什么？与数据库的连接不断出现故障，我不确定出了什么问题。我是mule的新手，对java和spring没有太多经验。感谢您的帮助

下面是错误的堆栈跟踪

org.mule.common.MuleArtifactFactoryException: Error initializing
    at org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.doGetArtifact(SpringXmlConfigurationMuleArtifactFactory.java:149)
    at org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.getArtifact(SpringXmlConfigurationMuleArtifactFactory.java:49)
    at org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.getArtifact(SpringXmlConfigurationMuleArtifactFactory.java:39)
    at org.mule.tooling.metadata.api.utils.ConnectionTester.internalTestConnection(ConnectionTester.java:58)
    at org.mule.tooling.metadata.api.utils.ConnectionTester.testConnectionFor(ConnectionTester.java:92)
    at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction$1$1.run(TestConnectorConnectionFromMuleConfigAction.java:65)
    at java.lang.Thread.run(Unknown Source)
Caused by: org.mule.retry.RetryPolicyExhaustedException: Error trying to load driver: ${osas-jdbc.classname} : ${osas-jdbc.classname} (java.sql.SQLException)
    at org.mule.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:105)
    at org.mule.transport.AbstractConnector.connect(AbstractConnector.java:1616)
    at org.mule.transport.AbstractConnector.start(AbstractConnector.java:428)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.mule.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:225)
    at org.mule.lifecycle.RegistryLifecycleManager$RegistryLifecycleCallback.onTransition(RegistryLifecycleManager.java:276)
    at org.mule.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:155)
    at org.mule.lifecycle.RegistryLifecycleManager.fireLifecycle(RegistryLifecycleManager.java:126)
    at org.mule.registry.AbstractRegistryBroker.fireLifecycle(AbstractRegistryBroker.java:80)
    at org.mule.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:120)
    at org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:94)
    at org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:90)
    at org.mule.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:72)
    at org.mule.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:64)
    at org.mule.DefaultMuleContext.start(DefaultMuleContext.java:255)
    at org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.doGetArtifact(SpringXmlConfigurationMuleArtifactFactory.java:130)
    ... 6 more
Caused by: org.mule.transport.ConnectException: Error trying to load driver: ${osas-jdbc.classname} : ${osas-jdbc.classname} (java.sql.SQLException)
    at org.mule.transport.jdbc.JdbcConnector.getConnection(JdbcConnector.java:258)
    at org.mule.transport.jdbc.JdbcConnector.doConnect(JdbcConnector.java:377)
    at org.mule.transport.AbstractConnector$5.doWork(AbstractConnector.java:1556)
    at org.mule.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:67)
    ... 24 more
Caused by: java.sql.SQLException: Error trying to load driver: ${osas-jdbc.classname} : ${osas-jdbc.classname}
    at org.enhydra.jdbc.standard.StandardDataSource.getConnection(StandardDataSource.java:184)
    at org.enhydra.jdbc.standard.StandardDataSource.getConnection(StandardDataSource.java:144)
    at org.mule.transport.jdbc.JdbcConnector.getConnection(JdbcConnector.java:254)
    ... 27 more

---

这就好像您没有通过使用Mule的属性加载机制（即在类路径的根目录下名为

Mule app.properties

的文件）或使用Spring的

上下文：属性占位符

Ok为

${osas jdbc.classname}

提供值一样。它在解析该属性时遇到问题。但是，我创建的用于保存所有全局项的流确实有一个属性占位符，该占位符引用该文件，并且该文件位于生成路径中。当我尝试在引用全局组件的另一个流中使用“测试连接”按钮时出现错误。我认为“测试连接按钮”不理解参数化配置。您是对的，它不理解。一旦我用实际值替换了它们（并且发现我必须在URL中转义-），它就起作用了。如果Mulesoft的任何人正在阅读此文章，请将此作为改进mule studio的一个机会。嗯，这显然已经解决了：请尝试最新版本。他们可能已经在SalesForce连接器上修复了它，但当您使用spring bean创建数据源时，它仍然损坏。我正在使用studio 3.5.0构建201310031601。我是在10/24下载的。