Camel 2.12.1 org.xml.sax.SAXParseException

Hi, in camel 2.12.1 when split a message this kind of xml tag doesn't work, meanwhile in camel 2.11.0 works fine: org.xml.sax.SAXParseException; XML documents structures must start and end within the same entity. If I add: works fine. Is suppose to be the expected behaviour? Thanks in adva

Re: Camel 2.12.1 org.xml.sax.SAXParseException

Hi, the input is: <-this kind of tag doesn't work. <---this works. The splitting route:

Re: How to retrieve only the last message from 10 messages passed to queue

Hi, take a look to advisory messages for activemq. -- View this message in context: http://camel.465427.n5.nabble.com/How-to-retrieve-only-the-last-message-from-10-messages-passed-to-queue-tp5743024p5743037.html Sent from the Camel - Users mailing list archive at Nabble.com.

Sql component headers and body in query.

Hi, I have the following sql endpoint: http://camel.465427.n5.nabble.com/Sql-component-headers-and-body-in-query-tp5743260.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Aggregator, beyond the simple string example

Hi, I did long time ago a test to add a child node to an xml root, you could modify it. public class XmlAggregator implements AggregationStrategy { public Exchange aggregate(Exchange oldExchange, Exchange newExchange) { Document oldBody = oldExchange.

Netty consumer fixed message size.

Hi, I'm sending a 100 bytes array to a netty consumer. Is there a way to post a message in the route each 100 bytes received? I tried with a FixedLengthFrameDecoder of 100 bytes, but sometimes I receive more than 100 bytes. Thanks. -- View this message in context: http:

Re: Netty consumer fixed message size.

Thanks Claus for your answer. I'm sure I'm sending blocks of 100 bytes. You are right, sometimes is posting to the route two or more of this blocks together. Is there a way to ensure that each 100 bytes received, the netty component will post a new message? Or I have to create a custom decoder wi

Re: Netty consumer fixed message size.

Hi, thanks again claus. My idea was to send first a 100 length packet with the number of (100 length) packets, post them individually in the route and aggregate them. -- View this message in context: http://camel.465427.n5.nabble.com/Netty-consumer-fixed-message-size-tp5750868p5750923.

Camel transacted route from JMS to JDBC

Hello I tried to create a transacted route, but after 7 retries the message is discarded and if the process is killed the message is lost. Setting the transacted parameter, the vm connector is repeatedly starting/stopping. Why happens this?

Keep the same message in a queue after consuming it.

Hi, is possible to consume a message from a queue in ActiveMQ and keep it in the queue for the next consumption of the same consumer? And is possible to override a message? I know that is not the goal of Camel and ActiveMQ. But I'm trying to use INOUT pattern and keep the message for future use. So

Re: Keep the same message in a queue after consuming it.

Thanks for the fast answer. I can't send the message back, because that means if I send a new message to the queue example.A from file, the sent back message will be consume before. I would like to have something like a LIFO in the queue example.A. And If there is no new message, keep consuming the

Re: Keep the same message in a queue after consuming it.

Exactly that, keep procesing the same message again and again until there's a new one. I know sounds strange for camel, but I need to write the same message until there's a new version. I tried with file component with let me override it. But I need to get the message in a producer. Many thanks :)

Re: Keep the same message in a queue after consuming it.

Thanks for the tips, I will try it! -- View this message in context: http://camel.465427.n5.nabble.com/Keep-the-same-message-in-a-queue-after-consuming-it-tp5739214p5739235.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Keep the same message in a queue after consuming it.

Finally I made it using content enricher, <-this override the file, so I always get the last one. <--this don't consume the file, so I have always the message. Finally I use file component, because its easier for users to open a simple xml file to se

Re: Keep the same message in a queue after consuming it.

The example above will not write the same file again and again, when you set noop=true camel set idempotent as well. So this line is now: <--this don't consume the file, so I have always the message. Hope this help. -- View this message in context: http://camel.465427.n5.nabble.com/Keep-the-s

Sql-stored: return clob

Hello, is it possible to return a java.sql.clob with the sql-stored component? I tested it adding a new parameter with a specific clob treatment: in components\camel-sql\src\main\java\org\apache\camel\component\sql\stored\TemplateStoredProcedure.java declareParameter(new SqlOutParameter(outPara

On exception notify first error.

Hello, is there a way on the on exception or in the error handler to send a message one time and keep retrying? Something like this but with error handler or on exception. java.sql.S

Re: On exception notify first error.

Thanks for the help. I came with the following solution: public class ErrorHandlerNotifier implements Processor{ Logger logger = LoggerFactory.getLogger(ErrorHandlerNotifier.class); private String destination; private final String DEFAULT_DESTINATION = "activemq:MAILING";