You are right. The type define in the interface is E but unfortunately in
the code, we are using String as type
1) constructor of idempotentconsumer defines the type as String
public IdempotentConsumer(Expression messageIdExpression,
IdempotentRepositoryString idempotentRepository,
Hi
I think its historical reasons with using strings first in Camel.
You are welcome to log a ticket to get this improved in a future release
On Thu, May 22, 2014 at 9:12 PM, David Karlsen davidkarl...@gmail.com wrote:
IdempotentConsumer demands that the messageId is a string:
final String
Hi
Yeah a good idea is to check the unit tests for camel-freemarker for examples.
Also take a note that Camel stores various information from the
Exchange etc. and provides that to freemarker in the process method.
We use Camel Integration framework to develop our integration projects and
deploy them into Jboss Fuse container. We have a consumer end point as ftp.
Route looks as follows
route errorHandlerRef=INVIntegration_myDeadLetterErrorHandler
streamCache=true
from
Done: https://issues.apache.org/jira/browse/CAMEL-7461
2014-05-23 8:48 GMT+02:00 Claus Ibsen claus.ib...@gmail.com:
Hi
I think its historical reasons with using strings first in Camel.
You are welcome to log a ticket to get this improved in a future release
On Thu, May 22, 2014 at 9:12
I couldnt fing find any way to resolve the issue because my component is FTP
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-lock-while-multiple-routes-polling-from-same-file-endpoint-tp5751467p5751508.html
Sent from the Camel - Users mailing list archive at
On Fri, May 23, 2014 at 10:54 AM, Jishnu jishnu.prat...@wipro.com wrote:
I couldnt fing find any way to resolve the issue because my component is FTP
The FTP component extends File component, so many of the options apply
to it too.
--
View this message in context:
Hello,
I have an issue with a gracefull shutdown of a route containing an exec
command, because the route is stopped after the exe command and what follows
is not processed.
With a sample it will be esasier to undersand:
route
process ref=process1/
to uri=exec:mycommand/
process
Notice from Camel 2.10 onwards the read locks changed, fileLock and rename
will also use a markerFile as well, to ensure *not picking up files that may
be in process by another Camel consumer *running on another node (eg
cluster). This is only supported by the file component (*not the ftp
You cannot provide a reason why a rollback happens in the TX API.
There is no rollback(String message) api for that.
You need to record this somewhere else if you want to use that.
Or do your own kind of TX rollback.
On Thu, May 22, 2014 at 11:00 PM, kraythe . kray...@gmail.com wrote:
Hi all,
I'm fairly new Camel user, but I'm pretty sure this is an issue:
I'm using a POJO Aggregator to aggregate the response from an Enrich
EAI. The strategy method has two parameters, one for the 'oldExchange'
message body and the other for the 'newExchange' message body; in my
case a Map and
You need to turn on allowNullBody or something like that
On Fri, May 23, 2014 at 11:33 AM, Radu Badita radu.bad...@gmail.com wrote:
Hi all,
I'm fairly new Camel user, but I'm pretty sure this is an issue:
I'm using a POJO Aggregator to aggregate the response from an Enrich
EAI. The strategy
Hello Claus,
The problem is that the route is shut down before the timeout.
It's seems to me that Camel thinks route is finished after running the exec,
despite there is still some task to do in the route.
Thanks.
--
View this message in context:
Hi,
I'm trying to use the properties substitution in my tokenizer with no
success.
I've also just seen that the camel-spring.xsd definition does not declare:
xs:anyAttribute namespace=##other processContents=skip/
In many complex types, so spring is not able to use the defined 'prop'
namespace
What version of Camel do you use? And have you tried with latest release.
On Fri, May 23, 2014 at 1:17 PM, carlo cancellieri
c.cancelli...@proximainformatica.com wrote:
Hi,
I'm trying to use the properties substitution in my tokenizer with no
success.
I've also just seen that the
I'm using the master branch so I'm on 2.14-SNAPSHOT
2014-05-23 13:18 GMT+02:00 Claus Ibsen claus.ib...@gmail.com:
What version of Camel do you use? And have you tried with latest release.
On Fri, May 23, 2014 at 1:17 PM, carlo cancellieri
c.cancelli...@proximainformatica.com wrote:
Hi,
Hi
Are you sure you do it correctly according to
http://camel.apache.org/using-propertyplaceholder.html
On Fri, May 23, 2014 at 1:27 PM, carlo cancellieri
c.cancelli...@proximainformatica.com wrote:
I'm using the master branch so I'm on 2.14-SNAPSHOT
2014-05-23 13:18 GMT+02:00 Claus Ibsen
Claus,
I think so.
If you kindly want to check here:
https://github.com/ccancellieri/camel_poc/blob/master/src/main/resources/META-INF/spring/camel-context.xml#L79
(at line 79) is commented out what I was trying to use (with no success).
As you could see I'm using it in the file endpoint url and
Hello everyone,
I'm currently working on error clauses and I got some strange behaviour
with camel in Scala. I would really enjoy having some feedback on what
I've tried to do because I haven't found any help on that. I saw Java
example that seamed to work and it's really currious for me.
Hi Claus,
Thanks for the reply. I have successfully started activemq embedded in
jboss-fuse.
Now from my application which is camel based I want to send receive messages
to that queue.
For the same I have coded which I mentioned in my 1st post. When I install
my application a lot of jasper,
Hello,
I wanted to ask, if it's not too much trouble, if anyone could help me with
this issue or give any idea so I can advance in my research.
I think that the problem could be in Camel since the Exception arrives to
the Camel classes of the CXF component as the exception trace of my previous
Thanks for the reply, but allowNullBody is not under user control as
it is set in AggregationStrategyBeanInfo(99) when calling:
Expression newBody = ExpressionBuilder.mandatoryBodyExpression(newType);
because mandatoryBodyExpression() just calls
mandatoryBodyExpression(type, false) where the
Hi
See bottom of this page about no data
http://camel.apache.org/aggregator2
On Fri, May 23, 2014 at 3:06 PM, Radu Badita radu.bad...@gmail.com wrote:
Thanks for the reply, but allowNullBody is not under user control as
it is set in AggregationStrategyBeanInfo(99) when calling:
Expression
Hi
The Camel scala DSL could use some love from some Scala fans. So any
contributions and improvements is welcome.
On Fri, May 23, 2014 at 12:59 PM, Christophe Pache
christophe.pa...@crossing-tech.com wrote:
Hello everyone,
I'm currently working on error clauses and I got some strange
Hi
Ah yeah we do not have support for @XmlAnyAttribute on the
ExpressionDefinition which is what the tokenizer etc is based upon.
So to support that we need to add that into the model, and also allow
org.apache.camel.model.ProcessorDefinition#resolvePropertyPlaceholders
to resolve from
Hi
For questions about JBoss Fuse, then please use their user forum for that
http://community.jboss.org/en/jbossfuse
And the product comes with a number of quicstarts out of the box you
can take a look at.
For example there is a jms quickstart in JBoss Fuse 6.1, that uses
Camel and AMQ.
On Fri,
Checked the documentation and understood. Basically the attribute
AggregationStrategyBeanAdater.allowNullNewExchange has to be true. But
it doesn't work since the newExchange is not null, instead only its
in-message body is null. Therefore the following:
if (!allowNullNewExchange
I was able to figure out how to set headers and retrieve those variables in the
FreeMarker template. However, I'm still unable to access them in the SMTP
endpoint. Also, if I set the exception, I can't call ${exception.stacktrace}
in FreeMarker like I can in a simple transform. Here's what I
You can set the subject as a header, then the smtp will use that
Something like this (not wrote the code in this email)
.setHeader(subject, simple(Message Broker Error
${exception.getClassName()}))
On Fri, May 23, 2014 at 3:45 PM, Matt Raible m...@raibledesigns.com wrote:
I was able to figure
Yeah, I know the rollback doesn't work that way. That wasn't what I was
driving at. I am just trying to deal with a business problem of informing
the investigator why an exchange failed though means other than spelunking
in a verbose log file for clues. Sometimes one investigating a problem may
Hi
Maybe send the error details to another queue, and have a way to
correlate that message to the other message that goes into the DLQ.
Though its a bit tricky as AMQ handles the DLQ, and Camel only would
know if its the last attempt, if you use the JMSRedeliveryCounter to
know it was the last
That worked - thanks!
.setHeader(subject, simple(Message Broker Error ({{ESB_ENV}}) -
${exception.class.simpleName}))
.transform(simple(${exception.message}\n\nStacktrace
Details:\n\n${exception.stacktrace}))
.to(freemarker:/templates/mail/error.ftl)
On Fri, May 23, 2014 at 4:27 PM, Matt Raible m...@raibledesigns.com wrote:
That worked - thanks!
.setHeader(subject, simple(Message Broker Error ({{ESB_ENV}}) -
${exception.class.simpleName}))
.transform(simple(${exception.message}\n\nStacktrace
Details:\n\n${exception.stacktrace}))
Claus,
I've just opened the jira (with your comment):
https://issues.apache.org/jira/browse/CAMEL-7463
Do you accept any contribution (pull req) on this camel-core component
improvement?
Cheers,
Carlo
2014-05-23 15:24 GMT+02:00 Claus Ibsen claus.ib...@gmail.com:
Hi
Ah yeah we do not have
Hey all,
I have a route that produces a CXF Endpoint.
public class FooRoute extends RouteBuilder {
private String uri = cxf:/foo?serviceClass= +
FooService.class.getName();
@Override
public void configure() throws Exception {
from(uri)
Its an idea but I think I would run into the same problem. The rollback of
the failed transation would roll back the message to the details queue as
well. The problem is I need the write to the details or error queue to be
outside the transaction but the inbox and outbox should be in the
How are u invoking the webservice?
Are you using CXF framwork? If so please provide the CXF endpoint configs
Reji
--
View this message in context:
http://camel.465427.n5.nabble.com/Exception-calling-webservice-with-camel-tp5751464p5751548.html
Sent from the Camel - Users mailing list archive
37 matches
Mail list logo
