Okay but I have actually already started down that path (using the *DTO classes). I just couldn't see how they were linked to the brokerDTO. But I guess many of them are nested and that is why. (Unfortunately I tried the SslDTO first which is nested so I didn't see the connection.) So I guess the hard part is figuring out the nested links.
After looking at the KeyStorageDTO I see it has a lot of good SSL config info in it and it is linked to the BrokerDTO by the 'key_storage' field. This one is easy since it is not nested. (Wish I had started with this one since the connection to the Broker is obvious!) The SslDTO object must be used in one of the fields of the *DTO objects used in BrokerDTO. So I suppose the way to proceed is to look at all the fields I can set in the BrokerDTO object. Then look at all the objects that /these/ fields take and within these objects the fields they take etc., and eventually I should cover all the *DTO objects and see all possible configurations. I think I would like to contribute an example explaining that and demonstrating it (once I get it working). It's not particularly obvious but once you get a nack for the approach, it's pretty easy. Thanks for the confirmation! -- View this message in context: http://activemq.2283324.n4.nabble.com/How-to-configure-embedded-SSL-broker-using-just-Java-code-tp4674768p4674770.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
