Can someone please provide a basic working example with Camel and MongoDB
using the Spring DSL?
Thanks,
Robert
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-with-MongoDB-Spring-DSL-tp5738402.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
No there is no wildcard support in the direct component. The intention
is that there is only one consumer per endpoint. If you have wildcard
supports then you may end up with multiple consumers matching a
wilcard pattern. The direct is intended for one consumer only per
endpoint.
On Sat, Aug
Hi
Do you refer to the netty producers channel pool and when those
channels are idle?
I dont think we have exposed an API for that that you can easily use.
Though commons-pool ought to have APIs for onIdle so its possible
doable to expose a SPI API for end users to use, to allow them doing
Use stopOnException and rethrow the exception from the producer template.
On Fri, Aug 30, 2013 at 11:39 AM, Christopher Gardner
chris.r.gard...@gmail.com wrote:
So if I have the following:
from(direct:a).split(...).streaming().bean(myBean)
where myBean uses a producer template to send to
Hi
Good idea I logged a ticket
https://issues.apache.org/jira/browse/AMQ-4706
On Fri, Aug 30, 2013 at 4:49 PM, Marco Westermann marwesterm...@gmx.de wrote:
Hi Claus,
thank you for that advises. But nevertheless I think it would be good ( not
just for beginners ) if a warning is logged in
Hi
Yeah wonder if we could improve this in Camel, so .to(log:xxx) and
.log(foo) uses a logger created by the application bundle.
So if we let the application bundles classloader try to load the
logger as a class, and use that? Well we could try to experiment. Then
by default it still runs
Hi,
I am trying to use Camel (2.11.1) Redis component to subscribe to a channel
without success.
I have looked at the test case
org.apache.camel.component.redis.RedisConsumerIntegrationTest
By the way, the above test case is disabled by the Junit @Ignore.
My code below is a clone of
You should likely reference the service in your xml file
Then from Quartz point of view its just a regular bean id you refer
to, and not all the osgi filter syntax which it does not understand.
See the spring-dm docs about service registry references
And possible at Karaf / ServiceMix docs as
Hi,
I have already referred to the datasource (OSGI service) in the beans.xml:
reference id=dataSource interface=javax.sql.DataSource
filter=(dataSourceName=default) /
a) And I had already tried referring to the datasource using the reference
id, in quartz properties:
bean id=quartz
Thanks Pontus Ullgren ,
can you explain something about seda implementation, i go to url but am not
able to get much,
want to know how we define seda que and put the messages to it ? in my
given example
--
View this message in context:
Hi Shing,
How are you publishing messages to Redis? Is it with Camel producer or
with other custom code?
Also have you seen this http://stackoverflow.com/a/16498040
HTH
Bilgin
On 1 September 2013 09:46, Shing Hing Man mat...@yahoo.com wrote:
Hi,
I am trying to use Camel (2.11.1) Redis
I'm excited to announce that my book Instant Apache Camel Message
Routing is published!
Instant Apache Camel Message Routing will help you to get started
with Camel and Enterprise Integration Patterns in matter of hours. It
is a short, focused and practical guide to Apache Camel that provides
a
Hi Bilgin
Oh half time in footie games today and reading this great news.
Congratulations.
This is great for the Apache Camel project that more dedicated Camel
books is coming out.
You may want to add your book to the books list at:
http://camel.apache.org/books
On Sun, Sep 1, 2013 at 3:36
Hi Bilgin,
I publish to the channnel from the redi-cli command line client :
redis 127.0.0.1:6379 publish mychannel Hello
(integer) 1
redis 127.0.0.1:6379
I have not read the mentioned post in Stackoverflow.
After following the suggestion in the post and adding a serializer, my Camel
A simplified answer is that the seda queue is defined when you use it as a
from endpoint ie from(seda:start).
To send messages to it in your example simply use the producer template
just change so the message is send to the seda uri instead of the direct.
Best regards
Pontus
Thanks Pontus
Hi Robert,
There are only tests with the Java DSL.
I'll commit one with the Spring DSL and give you the link.
Regards,
*Raúl Kripalani*
Apache Camel PMC Member Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani |
Here it is:
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-mongodb/src/test/resources/org/apache/camel/component/mongodb/mongoBasicOperationsTest.xml;hb=8e2fb690
.
Hope it helps.
Regards,
*Raúl Kripalani*
Apache Camel PMC Member Committer | Enterprise Architect,
Great idea. I logged a ticket:
https://issues.apache.org/jira/browse/CAMEL-6694.
Regards,
*Raúl Kripalani*
Apache Camel PMC Member Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net
In a SOA-based solution, the middleware implemented by Camel would expose a
service over a standard transport/protocol like HTTP (SOAP or REST), JMS,
TCP, etc. This interface would ideally be driven by a contract.
Your producer application would then send messages via this transport to
the
Congratulations Bilgin! Will order a copy...
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
If I have two routes in separate files that depend on each other I'll get the
following error message:
org.apache.camel.FailedToCreateRouteException: Failed to create route
TestWhiteBox: Route[[From[context:blackbox:testBlackBox]] - [Log[Called
b... because of Failed to resolve endpoint:
Before converting the event to JSON, I would like to store some variables
from the event and later use them in a to: destination.
So, am using header to stash away the values prior to conversion. Is this
the best way of doing this, or should I be using properties?
camel:route
I'll check this out too - thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/throttling-a-restlet-endpoint-by-discarding-excess-requests-tp5738089p5738450.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Bilgin
This sounds really awesome, congratulations!
Babak
bibryam wrote
I'm excited to announce that my book Instant Apache Camel Message
Routing is published!
Instant Apache Camel Message Routing will help you to get started
with Camel and Enterprise Integration Patterns in matter of
Claus,
That Throttle - Otherwise pattern would be ideal.
If there is a feature voting function somewhere I can register this with?
--
View this message in context:
http://camel.465427.n5.nabble.com/throttling-a-restlet-endpoint-by-discarding-excess-requests-tp5738089p5738452.html
Hi,
How did you define the whitebox.xml?
You can using the import resource to include the camel context that you want to
use just like this.
import resource=classpath:META-INF/camel-routes.xml/
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com
Hi,
exchange.getIn().setHeader(CxfConstants.OPERATION_NAME, Invoke);
exchange.getIn().setHeader(CxfConstants.OPERATION_NAME, InvokeOneWay);
I am confused that some camel-cxf test classes set the
CxfConstants.OPERATION_NAME header like that above instead of the method
name to be invoked .
The operation name is the method name you want to invoke.
Invoke and InvokeOneWay are the SEI method name you want to use.
As camel-cxf is using CXF client to send the request, so we don't use the proxy
method directly to send the invocation.
--
Willem Jiang
Red Hat, Inc.
Web:
28 matches
Mail list logo
