You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2011/04/05 11:32:05 UTC

[jira] [Commented] (AMQ-3268) Cannot use tag in blueprint configuration

    [ https://issues.apache.org/jira/browse/AMQ-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015813#comment-13015813 ] 

Gary Tully commented on AMQ-3268:
---------------------------------

There is a workaround:{code}<blueprint>
  <broker>
    ...
    <sslContext>
        <sslContext 
          keyStore="#keystore" 
          keyStorePassword="password"
          trustStore="#truststore"
          trustStorePassword="password">
        </sslContext>
    </sslContext>
    ...
  </broker>

  <bean id="keystore" class="org.springframework.core.io.FileSystemResource">
    <argument value="${karaf.home}/etc/service.jks" type="java.lang.String" />
  </bean>

  <bean id="truststore" class="org.springframework.core.io.FileSystemResource">
    <argument value="${karaf.home}/etc/service.ts" type="java.lang.String" />
  </bean>

</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