MULE-7731 JMS transport should reuse javax.jms.Session, javax.jms.Messag...

...eProducer instances by default
Yes it will.  I can put something in to avoid this but it'll be ugly because it involves using a fake ConnectionFactory to pass the values configured on the <caching-connection-factory> back to the JMS connector to be used there.  Should I do this?  And if I do which username/password should take precedence? The ones on connector or the ones on caching-connection-factory?