[ 
https://issues.apache.org/jira/browse/ARTEMIS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Bertram reassigned ARTEMIS-608:
--------------------------------------

    Assignee: Justin Bertram

> Document how to add user-provided classes to Broker class path
> --------------------------------------------------------------
>
>                 Key: ARTEMIS-608
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-608
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>          Components: Broker
>    Affects Versions: 1.3.0
>            Reporter: Jiri Daněk
>            Assignee: Justin Bertram
>            Priority: Major
>              Labels: documentation
>
> Broker reads the {{lib}} directory in the broker home directory and a {{lib}} 
> directory **in the broker instance directory** and jar files in these 
> directories are put on the class path. To provide my own Interceptor or 
> something, it should be built into a jar and (together with all depending 
> jars) dropped into the instance's lib directory, so it can be found by the 
> broker.
> This deserves to be written up in the documentation. I believe that the only 
> place this is described (the part about the instance's lib at least) is 
> http://activemq.2283324.n4.nabble.com/Adding-custom-decoder-into-Artemis-classpath-td4707493.html.
> Appropriate place for this explanation might be be 
> {{docs/user-manual/en/using-server.md}}
> There are few references to it, I managed to find 
> {{docs/user-manual/en/intercepting-operations.md}} and 
> {{docs/user-manual/en/persistence.md}} which say
> {quote}The interceptors classes (and their dependencies) must be added to the 
> server classpath to be properly instantiated and called.{quote}
> {quote}Add the appropriate JDBC driver libraries to the Artemis runtime. You 
> can do this by dropping the relevant jars in the lib folder of the ActiveMQ 
> Artemis distribution.{quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to