Re: Coming to Grips with Blueprint
As said, those elements are custom elements made available by projects to extend the standard blueprint element set with more specific ones. Each project (camel, activemq, cxf, ...) should document its own namespaces. Karaf provides a few also (jaas, shell). On Sat, Sep 10, 2011 at 00:47, Geoffry Roberts geoffry.robe...@gmail.comwrote: All, I have read about blueprint. I have reviewed the schema for blueprint, I have the specification. I did not find any mention of the use of elements like camelContext... or broker... or whatever. Yet I see these elements being used in blueprint files with success. My question is, Is there any documentation that catalogs all this? What other elements are there? Thanks -- Geoffry Roberts -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
Re: Cellar Commands Not Appearing In Karaf Console When Equinox Used
I should have checked JIRA. I see the commands in the trunk version. thanks again, Gareth On Sun, Sep 11, 2011 at 3:15 PM, Jean-Baptiste Onofré [via Karaf] ml-node+s922171n3327471...@n3.nabble.com wrote: You are right Achim ;) Regards JB On 09/11/2011 07:55 PM, Achim Nierbeck wrote: Hi Gareth, it's a known already fixed bug ;) https://issues.apache.org/jira/browse/KARAF-841 it will be available with cellar 2.2.3 Regards, Achim Am 11.09.2011 06:42, schrieb Gareth: Hello, I am having a small problem running cellar with equinox. If I start karaf 2.2.3 fresh (felix) and do the following: features:install webconsole features:addurl mvn:org.apache.karaf.cellar/apache-karaf-cellar/2.2.2/xml/features features:install cellar I see all the cellar commands appear in the karaf console (e.g. cluster:config-list, cluster:config-proplist etc). If I do the same with a fresh karaf 2.2.3 equinox (I set the karaf.framework to equinox in config.properties), the cellar commands do not appear (though cellar appears to still be running as my two Karaf nodes find each other). Anything obvious I missed that would cause the cellar commands not to appear in the console? Anything obvious I can check to help debug this? thanks in advance, Gareth -- View this message in context: http://karaf.922171.n3.nabble.com/Cellar-Commands-Not-Appearing-In-Karaf-Console-When-Equinox-Used-tp3326416p3326416.html Sent from the Karaf - User mailing list archive at Nabble.com. -- Jean-Baptiste Onofré [hidden email] http://blog.nanthrax.net Talend - http://www.talend.com If you reply to this email, your message will be added to the discussion below: http://karaf.922171.n3.nabble.com/Cellar-Commands-Not-Appearing-In-Karaf-Console-When-Equinox-Used-tp3326416p3327471.html To unsubscribe from Cellar Commands Not Appearing In Karaf Console When Equinox Used, click here. -- View this message in context: http://karaf.922171.n3.nabble.com/Cellar-Commands-Not-Appearing-In-Karaf-Console-When-Equinox-Used-tp3326416p3329766.html Sent from the Karaf - User mailing list archive at Nabble.com.
Using Karaf to Consume JMS Messages
All, Where am I going wrong? I'm having trouble getting JMS to work between two machines both running Karaf. Clearly I'm missing something. ActiveMQ is running on my producer machine and I am able to see messages in the queue. I'm using the ActiveMQ web console to monitor the queue. The trouble is they are not being consumed. The blueprint for my consumer is shown below, it deploys without error and shows up as active in the Karaf web console. But the ActiveMQ console shows that there are no consumers being connected. The consumer blueprint is shown below followed by the blueprint for the producer. Thanks Consumer machine: blueprint xmlns=http://www.osgi.org/xmlns/blueprint/v1.0.0; bean id=jms class=org.apache.activemq.camel.component.ActiveMQComponent property name=brokerURL value=tcp://url_to_remote_broker:61616 / /bean camelContext xmlns=http://camel.apache.org/schema/blueprint; route from uri=jms:queue:ave / to uri=stream:out / /route /camelContext /blueprint Producer machine: blueprint xmlns=http://www.osgi.org/xmlns/blueprint/v1.0.0; bean id=jms class=org.apache.activemq.camel.component.ActiveMQComponent property name=brokerURL value=tcp://localhost:61616 / /bean camelContext xmlns=http://camel.apache.org/schema/blueprint; route from uri=timer:test?period=5000 / setBody constantAve Mundus!!/constant /setBody to uri=jms:queue:ave / /route /camelContext /blueprint -- Geoffry Roberts
