We have recently implemented URL schemas for ConnectionFactories on
Activemq6 and I'm currently extending that support through ACTIVEMQ6-7
<https://issues.apache.org/jira/browse/ACTIVEMQ6-7>


I then looked at how that's done on ActiveMQ5 and there's some refactoring
done through IntrospectionSupport (i) to set properties through the URL
properties.


I was thinking about using BeanUtils now instead of doing our own
reflection. That would make us to include another dependency towards
BeanUtils though.. and I'm always up to have the embedded version having as
little dependencies as possible. But I believe BeanUtils would be a small
add on to the dependency tree.


Does anyone see any reason against adding BeanUtils and doing our own
reflection instead?



(i):
https://github.com/apache/activemq/blob/trunk/activemq-client/src/main/java/org/apache/activemq/util/IntrospectionSupport.java

Reply via email to