Hi Brian, BootstrapServices in LCDS 2.5 are special services used to create Services, Destinations, and Adapters without needing any configuration files. This is what you need to do:
1- Create a class that extends AbstractBootstrapService. 2- In that class, implement initialize() method. In this method, you'll create your destinations using the LCDS Server APIs. 3- Register your class with LCDS by referencing it in the services section of services-config.xml: <service class="my.company.MyBootstrapService1" id="bootstrap1"/> Next time, LCDS starts up, it'll call the initialize method of MyBootstrapService1 where you create your destinations and these destinations will be available to your app. There will be BootstrapService examples in resources/config/bootstrapservices once LCDS is final. -Mete --- In [email protected], "klumikaze" <[EMAIL PROTECTED]> wrote: > > Our application currently uses a large number of queue destinations. We create the > destinations in the messaging-config.xml file and compile our app against the FDS > configuration files (and then upload to the J2EE container). There are 100+ queue > destinations defined in messaging-config.xml currently. > > Our Java backend creates these queues in ActiveMQ or JBoss (using the same queue > destinations as configured in messaging-config.xml) and pumps data in to them. > > I've read through the beta documentation and there is a section on "Configuring components > with a bootstrap service". Do we need to create a class that creates/exposes these queue > destinations to the Flex app, or can we just attach Flex consumers to queue destinations and > the new LCDS libraries will do the work for us? > > Any input you might have would be appreciated. > > Thanks, > > Brian >
