On Wed, May 21, 2014 at 8:46 AM, cgiera wrote:
> We also tried
>
> bean(Myclass.class, "myMethod");
> bean(new Myclass(), "myMethod");
> beanRef(Myclass.class.getName(), "myMethod", false);
>
> They all don't work, the instance is everytime the same.
>
> Just for my understanding, I thought beanRe
We also tried
bean(Myclass.class, "myMethod");
bean(new Myclass(), "myMethod");
beanRef(Myclass.class.getName(), "myMethod", false);
They all don't work, the instance is everytime the same.
Just for my understanding, I thought beanRef(...) will create a new instance
and bean(...) will create a "
On Wed, May 21, 2014 at 8:22 AM, cgiera wrote:
> Yes, we use beanRef(MyBean.class.getName(), "myMethodName") in all our
> routes.
> The bean is not configured via spring and until 2.11.0 a new instance of it
> was created for each camel message. In 2.13.0 the same instance is used for
> each came
Fine thanks for your fast response.
I will try the component and if there is a problem with camel 2.13.0 I will
get in touch with the author.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/OFTP2-component-in-camel-tp5751125p5751396.html
Sent from th
Yes, we use beanRef(MyBean.class.getName(), "myMethodName") in all our
routes.
The bean is not configured via spring and until 2.11.0 a new instance of it
was created for each camel message. In 2.13.0 the same instance is used for
each camel message.
Short answer: Yes :)
kind regards,
Christoph
On Wed, May 21, 2014 at 8:06 AM, cgiera wrote:
> Hello,
>
> thx for your response.
> Now I know that there are official components and external components, I
> didn't know that.
>
> Just for information, when a new version of camel is released, how keep
> these external components in touch with th
Hello,
thx for your response.
Now I know that there are official components and external components, I
didn't know that.
Just for information, when a new version of camel is released, how keep
these external components in touch with the new release? Is there a list or
something else where is ment
Hi
There is this ticket which is related to what you talk about
https://issues.apache.org/jira/browse/CAMEL-7434
On Tue, May 20, 2014 at 9:02 PM, bluewolfca wrote:
> I have a use case that I need help with in the Camel Aggregator.
>
> Timeout defines an amount of time to wait after each new mess
Hi
If you use dynamic request and response queues (eg use many queues
instead of few) and if those queues are not to be reused, then you
would need to close the resources when you are done.
So it would only make sense to reuse the producer template for queues
you want to reuse in the future.
And
Hi
And your beanRef you refer to is a FQN class name (not a bean id in a
spring xml file or something) and you want a new instance of that FQN
class to be created each time (eg prototype scoped) and therefore want
cache disabled?
And what you see in Camel 2.13.x is that its no longer prototype sc
Hi
Try without writing to the file, but just do a
from jms
to log
and see if that is faster.
As appending to the *same* file name happens sequentially in Camel.
On Wed, May 21, 2014 at 6:06 AM, nw31304 wrote:
> I am attempting to do something really simple: read from an ActiveMQ queue
> a
On Tue, May 20, 2014 at 11:34 PM, Poyan G wrote:
> Hello Pontus,
> How are you ? :)
> Actually that was the way I solved it, but I field that it should be an
> better solution on it,
> I don't now how much overhead it is to set the body as a header ?
> I think it should be an better way to set the
I've done a tcpdump, and it seems that regardless of the number of
concurrentConsumers I specify, only one TCP/IP connection is ever being
used. I guess what I'm trying to understand is how to use multiple tCP/IP
connections in parallel. Would I need to use some sort of thread pool or
SEDA compon
I am attempting to do something really simple: read from an ActiveMQ queue
and append the messages to a file. Each message is roughly 100 bytes in
length and the arrival rate is no more than 1000 messages per minutes. No
matter what I try, messages queue up on the broker because the Camel route
d
Sure:
PRUEBA
ccarri...@universales.com
The only difference that I can note is that I added weblogic.xml file to
make weblogic recognize and start the ap
Can you share the camel route with us?
Did you change anything between the application in the tomcat and the one in
the weblogic?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo
Hello I've been looking for a solution for this issue but I haven't found
anything yet, when I use the smtp port and send a mail on development
environment on Apache Tomcat it send it just fine, but I deploy my
application to Weblogic server and it starts to send the email but it has
all the header
Hello Pontus,
How are you ? :)
Actually that was the way I solved it, but I field that it should be an
better solution on it,
I don't now how much overhead it is to set the body as a header ?
I think it should be an better way to set the body in the sql statement.
Thanks
2014-05-20 23:20 GMT+02
Hello Poyan,
You could try something like this to assign a header the value of the
body and then use the header name.
--
http://camel.apache.org/schema/spring";>
id
body
--
Hope this helps
// Pontus
On Tue, May
Hi,
I am creating a JMS route programatically by following code :
from("jms:queue:OUTBOUND_QUEUE?concurrentConsumers=5&messageListenerContainerFactoryRef=msgListenerContainerFactory").processRef("mqprocessor");
I have class :
public class MessageListenerContainerFactoryImpl implements
MessageLi
Hello,
I have an route there I want to insert complete message in an row in the
database, the problem is that the insert statement want # header name or
body name, and to have body name my body need to be hashmap, my body is
just an String and I want to insert the complete string in to database.
W
I have a use case that I need help with in the Camel Aggregator.
Timeout defines an amount of time to wait after each new message that gets
applied to a specific aggregated exchange. Different aggregations will then
accumulate for different amounts of time depending on message rep rate.
Interval
Hi Claus,
Thank you for the response.
Our server is multithreaded web-application. It sends requests to the
multiple endpoints in separate threads.
Please see below the sample of the code.
private ProducerTemplate camelTemplate;
synchronized public List executeMultipleQueries(final String[]
hu
Hi,
I just updated a unit test[1] which shows you how to set up the schema,
BTW, the package name of the SoapJaxbDataFormat is
org.apache.camel.dataformat.soap.
[1] http://git-wip-us.apache.org/repos/asf/camel/diff/8ea12ce7
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: htt
Thanks I'll try it this way!
--
View this message in context:
http://camel.465427.n5.nabble.com/CSV-bindy-tp5751292p5751360.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
If you only need one time response, then stop the template after
usage. Otherwise it keeps resources "warn".
And see this FAQ too
http://camel.apache.org/why-does-camel-use-too-many-threads-with-producertemplate.html
On Mon, May 19, 2014 at 7:05 PM, elena wrote:
> Hi,
>
> Our company use Act
Thanks for your reply Willem.
It was good to know about the configuring the cache.
But are you sure this is the answer to my question about the threads?
Elena
--
View this message in context:
http://camel.465427.n5.nabble.com/ProducerTemplate-creates-too-much-threads-tp5751299p5751361.html
Hi,
in my camel-route i want to send a soap-fault as response in case of
exception. My Problem is i don't know how to create a SOAP-Fault using the
SOAPJaxbDataFormat. Currently i use this code:
private class ExceptionResponse implements Processor {
@Override
public void process(
Hi Claus,
thanks for your response.
Yes, I know, that the Apache CI server is quite busy and there is no guaranteed
delivery of snapshots to the repository. I was just curious, if there might be
a chance to get this out, since the Camel-Extra CI currently fails due to the
missing dependency.
Hi
snapshots is not guaranteed to be build and published there. There is
a CI server doing that but its rather busy building all the other 150
apache projects
https://builds.apache.org/
And it only published to snapshot if the build was complete etc.
If you want snapshot, then build from source
Hi
I just encountered, that camel-saxon 2.14-SNAPSHOT is currently not available
via the Apache snapshot repository [1].
Could anybody be so kind and check, why that component has not been deployed to
snapshots yet?
Cheers,
Christoph
[1]
http://repository.apache.org/content/groups/snapshots
Hi
Not sure what happens. But we could try get that NPE fixed in Camel,
as that is a bug in Camel.
Fell free to log a JIRA.
And the stacktrace is handy so you are welcome to put that in the jira too.
On Tue, May 20, 2014 at 10:38 AM, Alberto Brosich
wrote:
>
> Hi,
> I have an exception from a
Hi,
Below is my aggragation route in java dsl:
.aggregate(new BodyAggregationStrategy()).
constant(true).
completionTimeout(3000).
to(target);
The same thing is working in spring dsl.But i want it in java dsl.
Exchanges(old and new) are coming to BodyAggregationStrategy class but i
thanks for the fast answer!
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-example-docs-does-not-work-tp5751346p5751350.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Camel Riders
I am back with a simple question I found to tough to answer myself: How do I
access the message body in a typesafe manner like in the TODO comment below?
Obviously implementing a processor works fine, but make things harder to read.
Thanks for advising,
Beat
Hi
The dot generation and visualization maven tool is deprecated and to
be removed in a future Camel release. The code has neither been
maintained for many years.
On Tue, May 20, 2014 at 1:15 PM, hxbx wrote:
> I try to understood the concept of generate visual docs using the example
> provided
Hi,
I'm using the Camel MQTT component with the following
uri (from karaf route-show):
http://camel.apache.org/schema/spring";>
uri="mqtt:testmqtt?host=tcp://localhost:1883&mqttTopicPropertyName=pippo&subscribeTopicName=topic/#"/>
in the JMS message there's no sign of the original to
I try to understood the concept of generate visual docs using the example
provided
with the camel sources (camel-example-docs).
Using camel 2.13.0, maven 3.2.1, java 1.7.0_55, GraphViz 2.28 in a Windows 7
environment.
GrapViz is available via the path variable.
The maven jobs described in the REA
It is not the change of https://issues.apache.org/jira/browse/CAMEL-6725
which is causing the problems, it's the change of
https://issues.apache.org/jira/browse/CAMEL-6724.
I've changed the Registry.getBean() method to the old version and tested
some of our routes again.
Now the beans get not cach
Hi
No have not heard about this. Feel free to log a JIRA ticket, and if
you got the stacktrace then that would be lovely if you could add that
to the JIRA.
On Tue, May 20, 2014 at 12:22 PM, JamesCG26 wrote:
> Hi,
>
> I have come across an issue with the Camel 2.13.1 source code when
> subscrib
Hi,
I have come across an issue with the Camel 2.13.1 source code when
subscribing to a qpid messages published by a non-camel producers. The error
happens with both Qpid C++ producer and also a python producer.
An Null pointer exception is thrown in the JmsBinding.extractHeadersFromJMS
on line 1
Your project works very well
Camel Route :
http://camel.apache.org/schema/spring";>
Model
import org.apache.camel.dataformat.bindy.annotation.CsvRecord;
impo
Hello, James!
Glad that it partially worked...
You could just unmarshall it buy SoapJaxb... and then to validate it inside
a processor or a predicate.
It is an artisan solution and more a workaround. But, may be, it will save
you some time.
--
View this message in context:
http://camel.465427.
Hi Willem,
yes, camel-soap and camel-jaxb are defined in pom.xml. Both have version
2.13.0, also in the generated war file under WEB-INF/lib
--
View this message in context:
http://camel.465427.n5.nabble.com/JAXB-Unmarshalling-of-soap-xml-including-schema-validation-tp5751290p5751339.html
Sent
Thanks for confirming Claus,
Logged in CAMEL-7448.
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: 19 May 2014 18:26
To: users@camel.apache.org
Subject: Re: throttle EIP - unchanged value
Hi
Yeah the doc is wrong - Camel has changed the throttler to allow a
Can you check if camel-jaxb and camel-soap jar in you class path are the same
version?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On May 20, 2014 at 3:27:16 P
Hello,
I've upgraded our application from camel 2.11.0 to camel 2.13.0.
First all looked fine, but now we are facing huge problems with all our
processes.
All our routes are caching the instances of our beans now, so we have a lot
of unwanted behavior in our application.
I've found an improvemen
Hi,
I have an exception from a ftp consumer only for few files. Camel
version is 2.13.1.
- It happens on few files (2 or 3). Remote directory contains many files
(many thousand)
- These few files have the same ownership and permissions of the others
and are not empty
- I stopped the application
Hello Willem, hello akoufoudakis,
thanks for your both answers! When using method setSchema Compiler says "the
method setSchema(String) is undefined for the type SoapJaxbDataFormat".
Casting does also fail.
trying akoufoudakis idea seems to work partly. After sending soap-xml
validator initially
Hi,
You need to make sure the json String is encoded with UTF-8.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On May 18, 2014 at 11:53:34 AM, jysemel (jyse...@qq
I just updated the XSLT documentation to indicate that the
CamelXsltResourceUri has been removed and that dynamic URI should be
used instead.
Perhaps the information about CamelXsltResourceUri should be
completely removed but for now I left it for those users that run a
dated version of Camel.
//
51 matches
Mail list logo
