Github user ricardozanini commented on the issue:
https://github.com/apache/activemq-artemis/pull/2241
Justification behind use of JMS Pool:
> The JMS pool provides configuration capabilities not available in the
CachingConnectionFactory and prevent certain not ideal uses like caching
consumer which one should really never do. The code does not preclude you from
using the CachingConnectionFactory at all and you can use standard Spring bean
trickery to control what is created in you app if you want so if you really
need to use CachingConnectionFactory. The PooledJMS library also provides JMS
2.0 functionality which is useful for those want that.
I'm going to add it to the README to make it clear to users. I'll correct
the Travis issues and stash the commit to be consider to be merged.
Thanks @michaelandrepearce and @jbertram!
---
