Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1289061208.1210783904068.JavaMail.jira@brutus>
Date: Wed, 14 May 2008 09:51:44 -0700 (PDT)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-1724) Allow ssl context configuration
 through spring/xbean
In-Reply-To: <1296625218.1210705663512.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Gary Tully commented on AMQ-1724:
---------------------------------

take that back, the fact that SslTransportFactory is brokerServiceAware ensures that once a broker listens/binds to an ssl address, the brokers SslTransportFactory will be initialised and used for subsequent Ssl comms.
So long as all listening is done before client side connecting, networks etc, it will work nicely.
thanks hiram.

> Allow ssl context configuration through spring/xbean
> ----------------------------------------------------
>
>                 Key: AMQ-1724
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1724
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Gary Tully
>             Fix For: 5.2.0
>
>         Attachments: AMQ-1724.patch
>
>
> amq ssl works with the javax.net.ssl system properties and can be configured via SslBroker without the system properties as shown in AMQ-1665. It would be better if it was possible to configure via spring or xbean.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.