Yes, I am talking about the URI for acceptor element. For example,
<acceptor
name="netty-ssl-acceptor">tcp://0.0.0.0:####?sslEnabled=true;keyStorePath=${hornetq.remoting.netty.ssl.keystore.path};keyStorePassword=${xxx};trustStorePath=${hornetq.remoting.netty.ssl.truststore.path};trustStorePassword=${xxx}</acceptor>
Here if ${hornetq.remoting.netty.ssl.keystore.path} resolves to C:\Program
Files then due to the space in the middle, the server fails to start. This
worked in HornetQ, perhaps because the paths were passed in as attribute
values, not a URI.
Of course, if the path is encoded, i.e. C:\Program%20Files, then things are
fine. Again, hornetq seemed to have tolerated it.
I am using Artemis 1.4.0.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Dynamic-broker-xml-include-properties-tp4718825p4718966.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
