Hi Alex, There is no wiki article for embedding 6.0 and 6.1. I while ago I built some examples for embedding 6.1. You can have a look at them at JIRA [1]. Some explanations for the examples are provided in JIRA comment [2].
What are the reasons behind your need to use 6.0 and 6.1? Please note, both of them have some issues with direct memory management. The details in JIRA [3]. The issues have been mitigated in latest 6.0.x and 6.1.x versions but they have been fully resolved only in 7.0. Thus, I would like to suggest replacement of 6.x with 7.0. Kind Regards, Alex [1] https://issues.apache.org/jira/secure/attachment/12863656/embedded-broker-example.tar.gz [2] https://issues.apache.org/jira/browse/QPID-7747?focusedCommentId=15971267&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15971267 [3] https://issues.apache.org/jira/browse/QPID-7753 On Thu, 13 Dec 2018 at 00:02, Alex O'Ree <[email protected]> wrote: > > The wiki article worked perfectly thanks!. Is there an equivalent for > versions v6.0.0 and v6.1.0? > > On Wed, Dec 12, 2018 at 7:19 AM Alex O'Ree <[email protected]> wrote: > > > sweet, thanks! > > > > On Mon, Dec 10, 2018 at 4:39 AM Oleksandr Rudyy <[email protected]> wrote: > > > >> Hi Alex, > >> > >> You can have a look at another example of embedding Qpid Broker-J [1] > >> where broker is started using dependencies to broker-core and amqp > >> protocol plugins. > >> This approach is handy when you do not need logback dependencies and > >> have already logging settings configured in your test framework. > >> > >> The Qpid Broker-J system tests have been re-factored to follow similar > >> approach. For example, you have a look at implementation [2] of > >> BrokerAdmin which is started QpidTestRunner [3]. > >> > >> Kind Regards, > >> Alex > >> > >> [1] > >> https://cwiki.apache.org/confluence/display/qpid/How+to+embed+Qpid+Broker-J > >> [2] > >> https://github.com/apache/qpid-broker-j/blob/master/systests/systests-utils/src/main/java/org/apache/qpid/tests/utils/EmbeddedBrokerPerClassAdminImpl.java > >> [3] > >> https://github.com/apache/qpid-broker-j/blob/master/systests/systests-utils/src/main/java/org/apache/qpid/tests/utils/QpidTestRunner.java > >> > >> On Sun, 9 Dec 2018 at 13:02, Alex O'Ree <[email protected]> wrote: > >> > > >> > Never mind, found it. For reference > >> > https://issues.apache.org/jira/browse/QPID-7486 > >> > see commit 0965d3d26b2598b2591032408cd6a490437b7383 Nov 2, 2016 > >> > > >> > On Sat, Dec 8, 2018 at 9:03 PM Alex O'Ree <[email protected]> wrote: > >> > > >> > > I use qpid during integration tests and basically fire up an embedded > >> qpid > >> > > server programmatically, then run my tests, then stop the server. I > >> have a > >> > > working setup for 6.0.0 and was attempt to update to a 7.x version and > >> > > found that the entry point i was using has been changed, specifically > >> the > >> > > 'Broker' and 'BrokerOptions' classes below. Is there an eqivalent > >> class > >> > > for the 7.x versions? > >> > > Also, is there a unit test or something similar in the qpid code base > >> that > >> > > i could track or follow for do something similar for future versions? > >> > > > >> > > Here's my old code for v6 > >> > > import org.apache.qpid.server.Broker; > >> > > import org.apache.qpid.server.BrokerOptions; > >> > > > >> > > org.apache.qpid.server.Broker broker = new Broker(); > >> > > BrokerOptions options = new BrokerOptions(); > >> > > options.setOverwriteConfigurationStore(true); > >> > > options.setStartupLoggedToSystemOut(true); > >> > > String file=new File(".").getAbsolutePath() + > >> File.separator + > >> > > "src/test/resources/config.json"; > >> > > System.out.println(file); > >> > > options.setConfigurationStoreLocation(file); > >> > > broker.startup(options); > >> > > > >> > > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
