I think what it boils down to is figuring out where you need to put the jar to make it available to the class loader in the java instance that is running your broker.
So, for example, on my Linux setup I have a directory /usr/share/activemq/lib that contains the jars needed to run ActiveMQ and I could place a jar there if I needed to add new deserialization classes. In my particular case I've got this running under a tanukiwrapper, and another option is to add a new directory to the /etc/activemq/activemq-wrapper.conf that points to a new jar directory. E.g., extending this block of configuration: # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 set.default.ACTIVEMQ_HOME=/usr/share/activemq wrapper.java.classpath.1=/usr/share/java/tanukiwrapper.jar wrapper.java.classpath.2=%ACTIVEMQ_HOME%/lib/* wrapper.java.classpath.3=%ACTIVEMQ_HOME%/lib/web/* wrapper.java.classpath.4=%ACTIVEMQ_HOME%/lib/extra/* wrapper.java.classpath.5=%ACTIVEMQ_HOME%/lib/optional/* wrapper.java.classpath.6=%ACTIVEMQ_HOME%/lib/camel/* Jim On Wed, Mar 30, 2016 at 11:54 PM xabhi <xabh...@gmail.com> wrote: > How do I make sure that this class is available at broker side? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Object-Message-to-json-transformation-not-working-tp4709447p4710145.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
