On Thu, Feb 11, 2010 at 8:33 PM, Julien D wrote:
>
> I have to look into the code to confirm this but I think that if you set the
> completionPredicate and you do not set the batchTimeout, the batchTimeout by
> default will not be active.
>
Sorry the current behavior is unfortunately that timeout
On Thu, Feb 11, 2010 at 10:15 PM, DanD wrote:
>
> I've noticed that if I use Spring's autoproxy capability
> () with an Aspect intercepting camel processors,
> that method calls with parameter annotations seem to get screwed up. I've
> noticed and replicated this on a number of different methods
I've noticed that if I use Spring's autoproxy capability
() with an Aspect intercepting camel processors,
that method calls with parameter annotations seem to get screwed up. I've
noticed and replicated this on a number of different methods of mine. Is
this an existing problem with Apache Camel
Above message this did not show up on forum..
--
View this message in context:
http://old.nabble.com/Identifying-and-processing-changed-file-when-noop%3Dtrue-tp27357357p27554335.html
Sent from the Camel - Users mailing list archive at Nabble.com.
why this does not show up
--
View this message in context:
http://old.nabble.com/Identifying-and-processing-changed-file-when-noop%3Dtrue-tp27357357p27554313.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I have to look into the code to confirm this but I think that if you set the
completionPredicate and you do not set the batchTimeout, the batchTimeout by
default will not be active.
lekkie wrote:
>
> I think there is a batchtimeout which by default is 1sec.
>
> So, whichever comes first 'd kic
See this unit test which works and uses the transferExchange option
https://svn.apache.org/repos/asf/camel/trunk/components/camel-jms/src/test/java/org/apache/camel/component/jms/JmsDeadLetterQueueUsingTransferExchangeTest.java
On Thu, Feb 11, 2010 at 2:58 PM, Nick Chistyakov wrote:
> Hello Cl
Hi
You can always put the caused exception to a Header as a String. The
JMS spec only allows a limited set of types to be used as JMS headers
(= JMS properties).
On Thu, Feb 11, 2010 at 2:58 PM, Nick Chistyakov wrote:
> Hello Claus,
>
> transferExchange=true will not work, I tracked it down to E
On Thu, Feb 11, 2010 at 4:58 PM, JohnMal wrote:
>
> Hi,
>
> I am using Camel 2.1.0.
>
> The behaviour does look similar to that described in the 1.5 gotchas in that
> the file to be picked up has not changed between scans. Will 2.1 ignore
> files that haven't changed on second and subsequent scan
On Thu, Feb 11, 2010 at 6:00 PM, mcrive wrote:
>
> In our use case we are sending feeds which gets updated quite often,
> this means almost the time the file won't be a new file but an update of an
> already existing one.
> While uploading the update the final file will be completely missing in th
I tried both XML and JavaDSL, results were consistent with XML and JavaDSL
XML
Java DSL
CamelContext context = new DefaultCamelContext();
context.addRoutes(new RouteBuilder() {
public void configure() {
from("file:src/
I think there is a batchtimeout which by default is 1sec.
So, whichever comes first 'd kick in.
Julien D wrote:
>
> Hi everybody,
>
> I have a question about aggregation with the completionPredicate. What
> does happen if somehow the predicate is never true ?
>
> For example if I have somet
Hi everybody,
I have a question about aggregation with the completionPredicate. What does
happen if somehow the predicate is never true ?
For example if I have something like that :
//Some camel code...
.aggregate().completionPredicate(header(Exchange.AGGREGATED_SIZE).isEqualTo(5)
and the AGGR
Hi, thanks for you response. Much appreciated.
I tried something different. I tried to instantiate the driver class from
inside a class in the bundle (this makes the bundle packager to add
net.sourceforge.jdbc... to the import package itself and when I tried to
start the bundle it says:
The
In our use case we are sending feeds which gets updated quite often,
this means almost the time the file won't be a new file but an update of an
already existing one.
While uploading the update the final file will be completely missing in the
target system.
In such a situation the way you perfor
Hmm...
I do not see it. Does the deployed jar contain the Driver class and does its
status show as installed when you do osgi/list?
Are there any other jars that the deployed jar depend on...?
In your bundle manifest, did you set the version to 1.2? In any case you do
not seem to mention a ver
Hi,
I am using Camel 2.1.0.
The behaviour does look similar to that described in the 1.5 gotchas in that
the file to be picked up has not changed between scans. Will 2.1 ignore
files that haven't changed on second and subsequent scans?
Ashwin Karpe wrote:
>
> Hi,
>
> If you are using Camel
I tried that and it still did not work.
My import package lookslike:
javax.jws,javax.wsdl,
META-INF.cxf,
META-INF.cxf.transport.nmr,
org.apache
This sounds suspiciously like a case of the problem being earlier in the DSL
and prior to reaching the processor getBody(). Have you checked the JAXB
object to not be null before passing it downstream...? Also, have you
checked if the payload is not being stomped somewhere earlier in the DSL
prior
Hi Claus,
I'll admit I did ask too soon, only 5 minutes after I submitted the
question I figured it out.
As for the question on why I wanted to use proxy with seda, I'm
essentially working on some examples of having domain code remaining
unchanged while changing the transports between objects, st
Hi,
If you are using Camel 1.X the following applies
Please check out http://camel.apache.org/file.html
http://camel.apache.org/file.html section "File consumer, scanning for new
files gotcha"
The file consumer scans for new files by keeping an internal modified
timestamp of the last consumed
Hi,
Please check out http://camel.apache.org/file.html
http://camel.apache.org/file.html section on common gotchas in file and
folder names
The file consumer scans for new files by keeping an internal modified
timestamp of the last consumed file. So if you copy a new file that has an
older mod
I am trying to copy files and change their contents based on an incoming JMS
message. If the same file name is passed in more then once the consumer
only picks up the file on the first message. I have tried putting
"&idempotent=false" on the url but it made no difference.
from("activemq:queue:c
Hi
Create a small sample of your project and attached it to a JIRA ticket.
Then we can take a look at it.
On Wed, Feb 10, 2010 at 4:27 PM, ariekenb wrote:
>
> I turned on DEBUG for org.apache.camel.component.jms.
>
> Here is what I see when I send to the temporary queue.
>
> My client is listen
no exception just return null object
2010-02-11 15:19:04,197 : Logger.process :
37b63738-e0c4-46aa-9906-a3a25805896f >>> (route1)
from(http://127.0.0.1:9090/greeting) --> <<< Pattern:InOut,
Headers:{org.restlet.http.version=HTTP/1.0,
CamelHttpUri=http://127.0.0.1:9090/greeting,
org.restlet.http.
Hello Claus,
transferExchange=true will not work, I tracked it down to Exchange
transformation to ActiveMQObjectMessage
ActiveMQSession.java:
1671: msg = (ActiveMQMessage)msg.copy();
ActiveMQMessage.java
public Message copy() {
ActiveMQMessage copy = new ActiveMQMessage();
Hi,
This looks very suspiciously like a bug. Can you please create a Jira entry
for this at
https://issues.apache.org/activemq/secure/Dashboard.jspa
https://issues.apache.org/activemq/secure/Dashboard.jspa
Cheers,
Ashwin...
Aleksey Masny wrote:
>
> Through camel-xmpp my message sended succ
Hi,
If the driver is a plain old jar it is possible to deploy it as such using
the wrap protocol for example
wrap:mvn:mygroupId/myartifactId/1.1 instead of handcrafting a manifest
entry... You need to install it in the maven repository first.
If the jar can be installed correctly and shows up
Hi,
Can you also post the exception that is being thrown...?
In addition is the payload being sent to the processor a serializable object
of GreetingRequestType.class?
You may want to introduce a log() in the DSL to get a sense of the contents
of the exchange
Cheers,
Ashwin...
Tapdur wrote
Hi,
Good answer James , Keep it up
James.Strachan wrote:
>
> On 10 February 2010 09:14, NagendraCorpus
> wrote:
>>
>> Hi,
>>
>> how to xmlvalidation using cameljavadsl , please explain how to do .
>
> see http://camel.apache.org/validation.html
>
> google can find that one quite easy :)
>
Hi community
in the process method, i want to get a body of type wich is generated by
xjc, how to pass to the getBody() the jaxb option ignoreJAXBElement="false"
(used in the unmarshall) ?
this line fail (within the correct object in the echange.in.value
attribute): GreetingRequestType user = (
Through camel-xmpp my message sended succesfully in standalone camel
application, but message not sends if application as a bundle deployed to
Felix Karaf. May be it is a bug in camel-xmpp component?
Apache Felix Karaf 1.2.0
Apache Camel 2.1.0
My route:
from("timer://foo?fixedRate=true&period=10
Hi
On Wed, Feb 10, 2010 at 9:53 PM, tfredrich wrote:
>
> Hi All,
>
> We're using the Restlet component to expose some public camel routes and are
> interested in leveraging the "connection: keep-alive" feature of http 1.1.
> However, no matter what we try, the response still includes "connection:
It was my fault, it is working now!
I forgot to assign the registry to the DefaultCamelContext
JndiRegistry jndi = new JndiRegistry(new JndiContext());
jndi.bind("myRetryBean", new RetryBean());
CamelContext context = new DefaultCamelContext(jndi);
looking into CamelTestSupport turned on
Hi guys,
I am trying to use spring to manage datasource and I am using
com.mchange.v2.c3p0.DriverManager.
I set my dynamicimport package to asterisk as shown below:
*
I have mssqlserver driver all in one (net.sourceforge.jtds) added as a
bundle, installed in servicemix with the ffg manifest:
M
You can use the destinationResolver option on the JMS endpoint to
implement a resolver that can lookup your custom MQ queue object.
http://camel.apache.org/jms.html
Which has a section about it and a link to this post
http://old.nabble.com/JMS-queue---JNDI-instead-of-physical-name-td24484994.html
[ I originally posted this as a MQSeries question, but really its a
Spring/Camel issue so I am posting again to garner more interest! ]
In Spring I have the following queue defined:
All of these arguments / properties are needed to make the queue work. Ho
Thanks Christian.
I have used those links already and checked again but they are limited in
their use of properties and constructor arguments.
I have it all working in Spring as I am allowed to control these aspects on
the class. I cannot see an equivalent mechanism to provide the same degree
o
You need to take a look at the code of CamelTestSupport to see how to
set up the Registry for the CamelContext, and how to bind the bean's
reference in the Registry?
Then update your code to set up a right Registry.
Willem
mcrive wrote:
what if I am not using CamelTestSupport?
Stephen Garga
what if I am not using CamelTestSupport?
Stephen Gargan wrote:
>
> If you're using CamelTestSupport you can do the following...
>
> @Override
> protected Context createJndiContext() throws Exception {
> Context jndi = super.createJndiContext();
> jndi.bind("myRetryBean", "s
40 matches
Mail list logo
