[
https://issues.apache.org/jira/browse/AMQ-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-3268.
-----------------------------
Resolution: Fixed
fix in http://svn.apache.org/viewvc?rev=1088944&view=rev
Resource replaced with String in the api such that the java api matches the
schema. sslContext can be used as expected in blueprint. {code}<blueprint>
<broker>
...
<sslContext>
<sslContext
keyStore="${karaf.home}/etc/service.jks"
keyStorePassword="password"
trustStore="${karaf.home}/etc/service.ts"
trustStorePassword="password">
</sslContext>
</sslContext>
...
</broker>
</blueprint>{code}
> Cannot use <SslContext> tag in blueprint configuration
> ------------------------------------------------------
>
> Key: AMQ-3268
> URL: https://issues.apache.org/jira/browse/AMQ-3268
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.5.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: blueprint, configuration, sslContext
> Fix For: 5.6.0
>
>
> Couldn't use the <SslContext> tag in blueprint configuration: setting a
> string attribute of the SslContext element resulted in the error "Cannot
> convert String to Spring Resource type" when I tried to use it in a blueprint
> file. It turns out that the Java source defines the property to be of Spring
> Resource type, not String.
> Pulling the Resource type out of the api and pushing it into the
> implementations will keep the schema String type matching the api which is
> more natural and will work easily with blueprint.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
