If I create a durable topic subscription using the jms or activemq components
(for example
activemq:topic:myTopic?clientId=client1durableSubscriptionName=subscription1),
does camel ever cause the durable subscription to be destroyed? In other
words will camel ever cause session.unsubscribe to be
I two beans named producer and consumer. Producer starts a java.util.Timer
in its init method to pop every 100 ms and send a message to a SEDA queue
(using a ProducerTemplate it got from @EndpointInject). Consumer has a
method to receive messages from the queue. Here's the camel route:
message.
Otherwise you can use some Camel API to find the processor and test
whether it is started with: isStarted()
On Wed, May 6, 2009 at 4:36 PM, ariekenb aaron.j.riekenb...@lmco.com
wrote:
I two beans named producer and consumer. Producer starts a
java.util.Timer
in its init method
Claus Ibsen-2 wrote:
Is there an easy way to know if all components/processors in a
CamelContext
are started? I can easily get the CamelContext injected into the
producer
bean, but I'm not sure what components I would need to check isStarted on
before sending a message.
Yeah I guess
at it.
On Sat, May 16, 2009 at 1:54 PM, ariekenb aaron.j.riekenb...@lmco.com
wrote:
Claus Ibsen-2 wrote:
Is there an easy way to know if all components/processors in a
CamelContext
are started? I can easily get the CamelContext injected into the
producer
bean, but I'm not sure what components I
...@gmail.com
wrote:
On Wed, Jun 24, 2009 at 8:50 PM, ariekenb aaron.j.riekenb...@lmco.com
wrote:
I just stumbled into an issue where using an @Consume annotation on a
bean
ended up creating 2 consumers when that bean was deployed in an OSGi
bundle
containing 2 camel contexts
Running ESB 4.1.0.2, the camel-mina feature will not install:
s...@root:features install camel-mina
ERROR CommandLineExecutionFailed:
org.apache.geronimo.gshell.command.CommandException:
org.osgi.framework.BundleException: Unresolved constraint in bundle 157:
package;
-s
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.mina/1.1.7_1
Next I tried installing the camel-mina-1.6.2-SNAPSHOT bundle I built and got
the error below:
s...@root:osgi install -s
file:///home/ariekenb/.m2/repo/org/apache/camel/camel-mina/1.6.2-SNAPSHOT/camel-mina-1.6.2
-s
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.mina/1.1.7_1
Next I tried installing the camel-mina-1.6.2-SNAPSHOT bundle I built and got
the error below:
s...@root:osgi install -s
file:///home/ariekenb/.m2/repo/org/apache/camel/camel-mina/1.6.2-SNAPSHOT/camel-mina-1.6.2
workable snapshot bundle's has the Ignore-Package section, I think
this will help Felix to ignore the MINA 2.0 bundle's exporting
packages.
[1]
http://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk/mina-1.1.7
Willem
ariekenb wrote:
Willem Jiang committed a change to add
I'm running apache-servicemix 4.1.0-psc-01-00RC1, using the included version
of ActiveMQ and Camel. I have some code that's receiving a message from an
ActiveMQ queue, then sending a message to the temporary queue it got from
JMSReplyTo.
@EndpointInject
private
I'm running FUSE ESB 4.2.0-fuse-01-00 with it's default version of Camel 2.2.
I'm trying to do something simple: I have a camel context defined in a
spring file:
camel:camelContext
id=aaron-test
/camel:camelContext
I inject it into a bean implementing
Willem -
I think I have found the source of my problem and a better fix.
I am creating the camel context in a spring XML file. I had FUSE ESB in a
state where both camel-spring and camel-spring-osgi bundles were loaded in
the container.
When both camel-spring and camel-spring-osgi bundles are
13 matches
Mail list logo
