I did a little more playing around. Discovered and verified a few different
things. First, I recall reading somewhere that the type mapping is being
cached (I think I read that). So when I played around with the JSON payload
being sent in I started to get mixed results and what was previously not
Thanks for confirming. I tested the logic and while there are no errors, the
value of the /time /property is being persisted as /null /in Mongo. I am
going to take a look at the converter classes to see if I can figure out how
that is possible. Any thoughts?
Again, thanks for the help on this!
Yes I can try that. To make sure I am on the same page is this what you are
asking for?
*Route:*
/
/
*JSON to send:*
/{ "time" : { "$date" : "2016-02-19T17:37:57.673+" } }/
Or do think we should not perform the convertBodyTo string?
Thank you for the quick response! I seriously
Any thoughts on my last post as to how we can use ISODates with camel-mongo?
Thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-insert-Date-String-as-date-in-MongoDB-tp5778310p5779035.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Thank you for the response and information. I believe I tried what is
recommended in the link that you provided. Below is a copy from the Logs via
the Karaf console. I hope the formatting is not too terrible. I can try and
provide it another way if necessary.
Pretty much the same result as I was
I would be interested in knowing the answer on how to do this as well. I
posted in a different thread and the datatype I am trying to do this with is
the ISODate built-in mongo type. I am using Spring DSL as well. Thanks!
--
View this message in context:
I am wondering if there is a good option for getting ISODates or any of the
other built-in MongoDB types to work within the context of Spring. For
example, given a very simple document:
/{ "time" : ISODate("2016-02-19T17:37:57.673+") }/
How might one get the ISODate to properly work with
I have searched through the user forum and done some research through Camel
docs as well, so if I missed the answer somewhere then I apologize.
I read that the File component is single threaded and what I would like to
be able to do, all while staying within Spring DSL, is to read file and fire
I think threads may be the way to go because i am using the File component in
a way that deletes the file upon successful processing. The WireTap route,
should it fail, means that my file is gone and I lose knowledge that the
File ever existed (I am still learning so perhaps that in and of itself
I just discovered this article
(http://www.davsclaus.com/2009/05/on-road-to-camel-20-concurrency-with.html).
I think this answers my questions above. It is the that takes over
the file exchange as handles the file completion piece. That tells me that
the deletion of the file will happen in the
I am hoping that this is possible, but I am struggling with figuring out a
solution.
What I need to know is, can I move a file that already exists on the file
system and to another folder using Spring DSL? I have a route that gets
kicked off by having a JSON message placed onto an ActiveMQ queue.
Nice! It looks like camel-exec will work for me. I just need to figure out
how to dynamically build up arguments for the move command. I tried using
the $simple{...} syntax, but that doesn't seem to be working. Thanks again
for help!
--
View this message in context:
Any idea as to why this does not seem to work?
setHeader headerName=ExecBinding.EXEC_COMMAND_ARGS
simple/C move
${body[FileDetails][FilePath]}\\${body[FileDetails][FileName]}
E:\\temp/simple
/setHeader
to uri=exec:cmd /
I am attempting to build the set of arguments
Hi Henryk,
I apologize for not providing more information. I guess I thought there was
enough context within the thread that one could understand what I was
referring to. Sounds like that was not the case.
The two attempts I made using Spring are as follows:
What Claus suggested:
transform
Yes, I started to realize that when I received an Ambiguous method call
exception in Camel. This is what I was trying to refer to when I said that
there are probably some limitations to the Simple language in that I am
unable to essentially add a cast to show my intent. For example I am
assuming
Thank you everyone for helping me work through this issue. I finally figured
out how to use groovy to solve for it.
This seems to be working for me.
transform
groovyrequest.body.replace(\\,)/groovy
/transform
Thanks again!
--
View this message in context:
Thank you for the response Claus. Cool that this is possible. I have been
trying to work with the Simple language in order to not have to dive into
the other scripting languages. I have had mixed results, none of which have
actually worked yet.
If I just take your example verbatim, then I getting
On Fri, Sep 14, 2012 at 5:03 PM, gramanero [hidden
email]http://user/SendEmail.jtp?type=nodenode=5719403i=0
wrote:
I am attempting to understand how the Camel File/File2 component works
as I
have a need to use this type of capability in an upcoming project.
Goal: Write a Camel spring
Is it possible to replace characters in a string via Spring DSL? I have a
file path and want to send that path to a resful service in the body;
however slashes in the path are preventing the packet from making it to the
restful service. If I escape the slashes, then the call works just fine. I
I am attempting to understand how the Camel File/File2 component works as I
have a need to use this type of capability in an upcoming project.
Goal: Write a Camel spring-based route that will detect files in a folder
structure, wait until the entire file has been written, and place an entry
onto
Sorry, once more piece of information...the appearing and disappearing of the
.camelLock file is continuous. It never stops unless I stop the route. Also,
I am running on Windows 7 O.S.
--
View this message in context:
I found this in the log as it relates to the issue with the .camelLock file.
Looks like there is a java.lang.NullPointerException being thrown. No clue
as to why this is happening though.
Fri Sep 14 2012 12:43:21 GMT-0400 (Eastern Daylight Time) ERROR Failed
delivery for exchangeId:
isn't rolling back if you handle the exception, is it?
On Thu, Jun 7, 2012 at 12:21 PM, gramanero [hidden email] wrote:
I have tested the case of using a route specific onException clause within
a
transaction and it appears to work as I would expect (or hope). So I have a
route
at my example.
On Fri, Jun 8, 2012 at 6:47 AM, gramanero [hidden
email]http://user/SendEmail.jtp?type=nodenode=5714181i=1
wrote:
No, it is not rolling back if you use the Handles element with a
constant value of true. If you use the Continue element then I believe
it
will roll back
I'm going through your example now. Only one problem for me, we are a
Micosoft shop. Much of the skill set of the developers is Microsoft-only and
very little Java experience. Having said that, I myself have developed in
Java for 5-years, but that was seven years ago. While the language is not
So in your example, what is the difference between the Purgatory count and
using the Redelivery capabilities built into ActiveMQ and Camel policies?
Maybe I'm missing something, but it seems like the logic wrapped around the
Purgatory concept is just keeping track of how many times a message has
Blueprint? Hmmm...I have not heard or seen that yet. lol...great. Another
rabbit hole for me to dive down into. ;-)
--
View this message in context:
http://camel.465427.n5.nabble.com/Transacted-vs-DeadLetterQueue-tp5713992p5714190.html
Sent from the Camel - Users mailing list archive at
Does anyone know if it is possible to interrogate an exception in Camel that
was thrown from a .NET-based endpoint (i.e. a .NET restful service)? I'm
thinking that since the restful service will throw the exception in either
JSON or XML format, that being a string based format (as opposed to
How do you get the message to bounce off the front of the queue? Can you
control whether the message is on the front or back of the queue? You
brought up an interesting point at the beginning of this thread that
indicated that a message could get stuck on the front of the queue thus
preventing all
Yes, that is correct and actually in my case that may be what I want to
have happen (i.e. the message gets put back onto queue A). However yesterday
I did some digging into the onException clause and I'm finding it very
useful. For example, if when something bad happens an exception is thrown,
I
I have tested the case of using a route specific onException clause within a
transaction and it appears to work as I would expect (or hope). So I have a
route that is transactional and the final endpoint in the route throws an
exception I forced my restful service to just throw an exception).
Thanks Claus.
So is collision avoidance a different mechanism than the exponential
back-off settings or do they work together?
--
View this message in context:
http://camel.465427.n5.nabble.com/Transacted-vs-DeadLetterQueue-tp5713992p5714060.html
Sent from the Camel - Users mailing list
Thanks for the response Christian.
I have been reading through the Camel in Action and ActiveMQ in Action books
most of the day today. I'm starting to get a better understanding of how
transactions work and that definitely seems like the way to go. Also, seems
like the DLQ and transactions work
I need to verify my understanding of the ThrottlingInflightRoutePolicy. I
have the following policy and route defined:
bean id=myPolicy
class=org.apache.camel.impl.ThrottlingInflightRoutePolicy
property name=scope value=Route/
property name=maxInflightExchanges value=1000/
Perfect. Thank you Claus! Your quick response is very much appreciated.
--
View this message in context:
http://camel.465427.n5.nabble.com/ThrottlingInflightRoutePolicy-tp5713970p5713973.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I'm wondering if there are any sort of best practices or pros/cons to using
either the dead letter queue or transactions when errors occur while pulling
off messages from a queue and attempting to route them to a cxfrs endpoint
that may not be available.
For example, say I have the following
Currently there is no need to perform any transforms on the request. Just a
straight pass through camel.
Sorry for my ignorance, but what would the route look like if I were to take
your suggestion of using the http endpoint to send the request?
Thank you for your response.
--
View this
Ok, after toying around with it I realized that I messed up the uri for the
cxfrs endpoint. I have it working now. I would still be interested in seeing
the route that send the request via the http endpoint, just to educate
myself more.
Thank you for all the help. The final route ends up looking
I am very new to FuseESB and the underlying technology stack, so I
apologize up front if I am not using the correct terminology when trying to
describe the issues we are running into. We are working on a proof of
concept to determine if FuseESB is the direction we want to go for some
internal
Thank you for the tip about removeHeaders. I was wondering if there was an
easier way to accomplish that. Very much appreciated!
What I noticed when initially trying to route the message from jetty to the
restulf svc is that the CamelHttpUrl was incorrect. What was logged in the
servicemix.log
40 matches
Mail list logo
