GitHub user michaelandrepearce opened a pull request:
https://github.com/apache/activemq-artemis/pull/1641
Sorting issue with BeanUtils picking up set/get props in JNDI - WIP-DO NOT
MERGE
Apply fix so that when using JNDI via tomcat resource it works.
Replace original extract of JNDIStorable taken from Qpid, and use
ActiveMQ5's as fits better to address this issue. (which primary use case is
users migrating from 5.x)
Refactored ActiveMQConnectionFactory to externalise and turn into reference
by StringRefAddr's instead of custom RefAddr which isnt standard.
Refactored ActiveMQDestinations similar
Refactored ActiveMQDestination to remove redundent and duplicated name
field and ensured getters still behave the same
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/michaelandrepearce/activemq-artemis
fix_jndi_tomcat_resource
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1641.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1641
----
commit d90294ad69c08f43e244b2ec9f8a4d3acf71293c
Author: Michael André Pearce <[email protected]>
Date: 2017-11-04T02:26:39Z
JNDI Tomcat Resource Properties
Apply fix so that when using JNDI via tomcat resource it works.
Replace original extract of JNDIStorable taken from Qpid, and use
ActiveMQ5's as fits better to address this issue. (which primary use case is
users migrating from 5.x)
Refactored ActiveMQConnectionFactory to externalise and turn into reference
by StringRefAddr's instead of custom RefAddr which isnt standard.
Refactored ActiveMQDestinations similar
Refactored ActiveMQDestination to remove redundent and duplicated name
field and ensured getters still behave the same
----
---
