Try to debug the crypto component and see if the jks file is referenced
correctly.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/Issue-with-Camel-Crypto-Signing-tp5764289p5764343.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Sry, I'm so bad :(.
We don't create a new camelContext by ourself, but it's never set in our
TemplateRoutes(a subclass of RouteBuilder).
Now if someone calls templateRoute.getContext() camel will create a new
(default)one, and not the "real" one is used.
The manual CxfEndpoint creation looks good
gt; Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
> On March 5, 2015 at 10:06:55 PM, cgiera (
> christoph.giera@
> ) wrote:
>> Hello,
&
itiveinformation
>
> Regards,
> -Yogesh
>
> On Thursday, March 5, 2015, cgiera [via Camel] <
> ml-node+s465427n5763673h92@.nabble
>> wrote:
>
>> There I have the same problem that the route is started, but the endpoint
>> is not callable via soapui or s
est$MyCxfEndpointConfigurer"
> />
> --
> 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 March 5
There I have the same problem that the route is started, but the endpoint is
not callable via soapui or smthg. The route is also not shown in our jmx
monitoring screen.
yogu13 wrote
> Hello Christoph,
>
> Please check the CxfEndpoint API in camel first!
>
> I would say you shouldnt be calling
It's an web application, context is started via a subclass of the
ContextLoaderListener.
camel-context.xml
http://camel.apache.org/schema/spring";>
The masterRoutesBuilder adds all routes to the context. Each route class is
a sub class of RouteB
How can I configure this endpoint correctly so that I don't loose any
parameter of my "normal" URI?
I've tried this:
But then the service is not available.
kind regards,
Christoph
yogu13 wrote
> I am assuming you are using java dsl.. in that case you create instance as
> below
>
> CxfEn
Ok, it's configured via spring:
But that's not an option for me, I have to add it programatically.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Cxf-How-can-I-change-the-namespace-of-my-incoming-message-tp5763634p5763640.html
Sent from the Camel - Users mailing lis
6
>
> --
> 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 March 5, 2015 at 4:41:4
I think it should work with the cxfEndpointConfigurer-parameter:
RouteBuilder configure method:
{raw}
JndiRegistry registry = (JndiRegistry) (
(PropertyPlaceholderDelegateRegistry)this.getContext().getRegistry()).getRegistry();
MyEndpointConfigurer myConf=
Hi all,
I have to change the namespace of the incoming messages to our webservice.
The consumer route looks like the following:
from("cxf:/myservice?serviceClass=myServiceClass")...
I've tried to add somehow an interceptor to this(parameter properties.in,
properties.inInterceptors?), but I don't
Thx for the quick response and solution.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Netty-Http-HttpHeaders-case-sensitive-tp5763157p5763231.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hello,
we are implementing a http camel route for receiving data from SAP.
The route consumes from a netty-http endpoint(from("netty-http...")).
Our tests with SoapUi worked fine, but when we tried sending data from the
SAP system the test failed with http 400 bad request.
After some research I f
Ticket created, see https://issues.apache.org/jira/browse/CAMEL-7536.
Looking forward to provide a patch.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-mail-content-transfer-encoding-configurable-tp5752504p5752791.html
Sent from the Camel - Us
Maybe something similar to the ContentTypeResolver is also a good solution
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-mail-content-transfer-encoding-configurable-tp5752504p5752744.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
ok, just for clarification what would be a good solution for this:
I've not mentioned that we need the content-transfer-encoding for the
attachments of the mail.
Some ideas from my side:
1. use a parameter like contentType, let's say content-transfer-encoding:
If this parameter is set ALL att
Hi,
thx for your response.
It's not mentioned in the documentation that stateless beans should be used.
I also think that it is quite misleading that the "beanRef" functionality
can be used(using the classname as string).
kind regards,
Christoph
--
View this message in context:
http://camel.4
Hello,
the camel mail componente determines the content-transfer-encoding itself
based on the content of the message.
We now have a customer we are only allowed to send messages where the
content-transfer-encoding is base64. As most of the messages haven't any
special characters camel determines 7
The problem occures in camel 2.11.0 and 2.13.0.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/split-with-bean-multithreading-problem-tp5752258p5752502.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I've a workaround for this issue:
I've introduced a new method which creates a new instance of the bean:
However, I still think the split with bean(Ref) behavior is wrong.
Should I create a ticket for this?
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabb
Hello,
most of our routes contain a split with bean functionallity.
For example:
.split().method(Myclass.class.getName(), "method")
or
.split(bean(MyClass.class.getName(), "method"))
Sometimes we got strange behavior in this routes and now I've found why:
Although the bean MyClass was given to t
Ticket is created: https://issues.apache.org/jira/browse/CAMEL-7452
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/beanRef-is-caching-instances-in-camel-2-13-0-unwanted-behavior-tp5751335p5751400.html
Sent from the Camel - Users mailing list archive
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 "
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
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
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
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
Hello,
I'm not able to find the OFTP2 component in an official camel release.(see
http://camel.465427.n5.nabble.com/Camel-Component-for-the-OFTP2-protocol-td2848614.html#a2849338)
Have I missed something or should i just add the (old) jar files from the
website mentioned in the post above?
kind
Hi Aki,
I have upgraded to 2.13.0 now and applied your patch of CAMEL-7388.
Everything looks fine so far.
Thanks for your help!
Kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/Split-XML-with-xmlTokenizer-and-add-root-element-tp5750237p5751060.html
I think I've solved the problem by adding the annotation @Addressing(enabled
= true, required = false) to the used webservice.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/cxf-how-to-add-wsa-addressing-with-cxf-someAddress-options-uri-format-tp5750
Hi,
maybe someone will correct me, but I think thats not an issue of the
camel-cxf component.
Cxf uses jaxb as standard binding and jaxb has a standard schema to java
type mapping:
See the chapter "Schema-to-Java Mapping" of the following link:
http://docs.oracle.com/cd/E19159-01/819-3669/bnazf/i
I see there are some changes between 2.11.0 and master regarding the
TokenXML* classes.
In the master version there is a "new" class TokenXMLExpressionIterator
where you did your changes, in 2.11.0 which i use there is only the
TokenXMLPairExpressionIterator.
Maybe you can be so kind and help me p
Hi,
cool stuff, I will patch it into my camel version.
Thx!
kind regards,
Christoph
Aki Yoshida-3 wrote
> as it seems the corresponding source files have not been linked to the
> jira ticket,
>
> you can find examples/test cases at:
>
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=t
I forgot to mention that the wsa addressing headers only cause problems when
the attribute mustUnderstand=1 is set.
--
View this message in context:
http://camel.465427.n5.nabble.com/cxf-how-to-add-wsa-addressing-with-cxf-someAddress-options-uri-format-tp5750440p5750484.html
Sent from the Camel
Hi,
I've to configure the wsa addressing feature on some of our webservice
consumers.
The routes look like the following:
from(cxf://someAddress?serviceClass=someClass)
.to(...)
Maybe I missed something but I've only found the wsa addressing
configuration via spring:
example:
...
Hi all,
should we create a camel jira issue for this?
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/Split-XML-with-xmlTokenizer-and-add-root-element-tp5750237p5750360.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hello,
I have to deal with large xml data in our camel application. In the camel
documentation I've found the splitting with the
xmltokenizer(split().xmlTokenize()).
First it looked fine for me, but then I noticed that there is no possibility
to add the root element to the splitted xml's.
Xml loo
Issue is created: https://issues.apache.org/jira/browse/CAMEL-6964
Our solution is working for the camel version we are using(2.11.0).
I'll provide this patch for the actual trunk version
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/FileConsumer-
We 've now tested with camel 2.12.1 and the behavior is still the same.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/FileConsumer-Deletion-of-done-file-s-tp5743106p5743172.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Should I open a ticket and maybe apply a patch?
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/FileConsumer-Deletion-of-done-file-s-tp5743106p5743173.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Thx for the response.
Yeah we use the moveFailed option to move the file into an errorFolder, but
the done file still appears in the source folder.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/FileConsumer-Deletion-of-done-file-s-tp5743106p574310
Hello,
we are having some issues with the deletion of done files when consuming
Files with the standard camel component.
First only one done file was deleted when the fileConsumer grabs more files
at once, this problem I've found in the forum. (We are using camel 2.11.0
and there was an issue wit
Hello,
it looks like we have found the problem:
http://www.mail-archive.com/cyrus-devel@lists.andrew.cmu.edu/msg01684.html
We use exactly the cyrus version mentioned in the link, it is not 100% sure
if this is the real problem, but we are setting up a server with cyrus 2.4.x
and run our tests aga
Hello,
I think I got it.
I didn't know that it is possible to add the same Runnable to the
ExecuterService multiple times.
Thx for your help.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/Adding-MultiConsumer-support-to-a-ScheduledPollEndpoint-S
Yes, that's a good hint.
>From your experience is it a viable way to implement it like this?
It looks strange to me to add new consumers in a consumer class.
Maybe there is some impact on the general functionallity if I don't create
consumers with the endpoint.createConsumer method or something
Yes, but I haven't found an easy way to add my consumer(when I extend from
ScheduledPollConsumer it is a Runnable) to the underlying executerService. I
think there should be an easy way but I haven't found it.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabb
Claus Ibsen-2 wrote
> They are not the same. The former is for allowing 2+ routes with the
> same endpoint, eg multiple consumers, eg:
>
> from A
> to B
>
> from A
> to C
>
>
> concurrentConsumers is for the same consumer, eg
>
> from A concurrentConsumers = 10
> to B
>
>> I have looked
Hello,
I have to write a new Camel component which should have the similar behavior
like the JmsComponent but I'm not allowed to use Jms(due customer
restrictions).
I want to use as much functionallity as possible from the standard
implementations in camel.
So I decided to extend from the Default
My last post is nonsense, I have looked at the wrong object.
When I change the endDoTry() to
it is working again.
I'm not sure if I should apply a patch for this, pls let me know if so.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/endDoTry-tp57
Ok, I see that the code of 2.11.0 also just returns "this", so it would be
the similar value as in our 2.6.0 version.
So is there a change in the behaviour of doTry/doCatch/doFinally in an
onException block?
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabbl
Hello,
I have found out that we have used patched version of 2.6.0:
was added to the ProcessorDefinition-class.
In camel 2.11.0 it looks slightly different:
and in the end() method there are some comments regarding doTry/doCatch:
Somehow it is not properly working I think.
kind regards,
Chri
Hello,
I'm upgrading from camel 2.6.0 to 2.11.0. It's a big step as 2.6.0 is pretty
old.
However some of our routes don't start anymore because of the exception:
The route looks like the following:
Should I just remove the endDoTry() or is there another possibility?
kind regards,
Christoph
Christian Mueller wrote
> Can you send me the entire log file. I need more context than only two
> lines...
Above of the 2 lines you can find a big part of the log file, I thought this
will be enough, but sure I can
send you the 30 MB zip files :).
Christian Mueller wrote
> Do you have multiple
Here is another part of the logfile where this problem occures:
Here is something really strange:
INFO | jvm 1| 2013/06/19 11:30:37 | 2013-06-19 11:30:37,237 [Camel
(camel) thread #2 - imap://] DEBUG - Polling mailbox folder:
imap://:143, folder=INBOX
INFO | jvm 1| 2013/06/19 11:30:37
Hello,
now with java mail 1.4.5 and log entries(have added slf4j_log4j.jar to
ensure debug messages occure):
It's the same behavior and the same log entries,
missing mail logs:
INFO | jvm 1| 2013/06/19 11:54:23 | * 2 RECENT
INFO | jvm 1| 2013/06/19 11:54:23 | * SEARCH
INFO | jvm 1
Hello,
I've updated our customers qa system to camel 2.11.0 and mail 1.5 now.
We've added some test routes to send mails to the mail box we are reading
from and had a look at it
if mails are missing.
After ~1 hour we saw that sent mails vs. received mails was not equal
anymore and analyzed the lo
Hello,
thx for the reply.
I've updated to camel 2.11.0 and java mail 1.5 before I've begun the
testing.
So all the log's from the previous posts are already from the newest
version.
On my local system I've tested the workaround with fetchSize=1, here both
versions 2.6.0 and 2.11.0 are working for
Hello,
thx for the reply.
But even if the consumer is not transaction secure, it should not happen
that mails are marked as seen but don't get processed. I haven't found why
this happens exactly, but I have described where it happens in my previous
posts. I'm wondering that no one had this behavio
A general question:
Is the camel mail consumer transaction secure?
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/MailComponent-MailConsumer-misses-Mails-tp5733010p5733918.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Seems like my workaround is not working 100% correctly.
We added the fetchSize parameter to the necessary routes on our customer
system and it looked really fine, but when 2 mails arrived within the same
second only one message get processed but two were marked as seen :(.
However on the customer s
.isOpen check. After this all fetched mails
are marked as seen, but only 1 message is processed.
cgiera wrote
> Even if I set the maxMessagesPerPoll option to 1, the fetchsize in this
> case is -1.
> So all messages will be looped in this case.
> In debug mode I have changed the val
I'm not sure if I'm on the right way, but I've found one thing which doesn't
work correct I think:
Even if I set the maxMessagesPerPoll option to 1, the fetchsize in this case
is -1.
So all messages will be looped in this case.
In debug mode I have changed the value of the fetchSize to 1 and onl
eam all messages are marked as seen.
kind regards,
Christoph
cgiera wrote
> Ok, this was a big mistake, when i set the maxMessagesPerPoll option to 1
> and the pollinginterval to 1 sec only every ~ 5th message will be
> processed!!
> The second test route sends every second 4 messages
code
segment where this goes wrong.
cgiera wrote
> The missing mails can be reduces when setting maxMessagesPerPoll to a
> small number, but it doesn't solve the problem.
>
> kind regards,
> Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/M
I have upgraded to camel 2.11.0(not all referenced libs but camel mail
component doesn't use any referenced libs) and mail 1.5.
The problem still exists in the new versions.
I will debug the MailConsumer now and I try to find out what's going on.
I believe there is something wrong with this code:
We are using java mail 1.4.4. I think this is pretty new although ~ 1 month
ago java mail 1.5 was released.
Short update from our testing/analyzing:
It seems the problem occures when mails are arriving on the mailbox while
MailConsumer is working.
I have created a test scenario where I loaded ~3
Hello,
hm, it is not a really big step from 14 messages to 10 ^^.
Or does this limiting of the messages changes the behavior of the
MailConsumer significantly?
Thx for your reply.
kind regards,
Christoph
Claus Ibsen-2 wrote
> Hi
>
> You can try using maxMessagesPerPoll=10 or something to limi
Hello,
due customer restrictions to java 5 we couldn't upgrade until now.
This restriction will now fall, so we can upgrade now.
However it is a big step from 2.6.0 to 2.11.0 and I already started the
upgrade process, but I'm facing big problems with the referenced lib's as
they are not integrated
Hello,
I'm facing strange problems when consuming mails from a cyrus mail server.
Some mails were not processed but appear as SEEN in the mailbox.
I've added the mail debug option to the route and I was pretty confused when
analyzing the log:
First poll is quite normal: 14 new mails, 14 get fetch
Claus Ibsen-2 wrote
> Instead of split().method, use split(method)
> eg supply the method call expression as a parameter. That helps the
> compiler.
Yes,
works fine for me. Thank you very, very much!!
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.
Hello,
I'm trying to get my route working which looks like the following:
The problem I have is that the compiler says "The method beanRef(String,
String) is undefined for the type Object" in the second split:
I replaced the .end() with .endSplit() and so the compiler was happy again,
but then
I've added the synchronized modifier to the RegistryBean.getBean() method and
the problem is fixed for now.
Hopefully I can upgrade to a newer version of camel in the near future.
kind regards,
Christoph
--
View this message in context:
http://camel.465427.n5.nabble.com/ClassCastException-usin
Claus Ibsen-2 wrote
>
> On Tue, May 29, 2012 at 2:44 PM, cgiera <christoph.giera@> wrote:
>
> You use an old version of Camel. You can upgrade to have this fixed.
>
>
> When Camel start the routes it initializes the resources and thus also
> bean / beanRef,
Claus Ibsen-2 wrote
>
> When using .bean in the DSL, then the bean is looked up / created once
> / etc when the route is being initialized / started.
> And thus there is no thread safe issue at runtime, as the beans is
> already created.
>
> When using bean with a class type, the bean is created
Willem.Jiang wrote
>
> What's the problem ?
> I don't think passing the bean object instance will introduce any
> further issue into camel-jms and camel-jpa components.
>
Perhaps I don't understand you correctly, but if i pass the object instance
like
I get problems with our whole implementat
cgiera wrote
>
>
> Willem.Jiang wrote
>>
>> BTW the bean DSL support to pass the object, can you use the Object
>> instead of the Class?
>>
>
> I'll give this a try and let you know. Would be nice if this works.
>
> kind regards
Willem.Jiang wrote
>
> The bean method should be thread safe, as the method will be called
> from different thread.
>
The getBean() method is not thread safe:
Just try it out:
You need 2 breakpoints in this method:
1. breakpoint at last if in line value = bean
2. breakpoint at line bean = v
I think I have found the problem:
The RegistryBean.getBean() method is not thread safe:
When I was debugging this method i notized that the bean member variable
changes every now and then. I think this happens because another thread
changes the member.
In the last if block of the me method I thi
cgiera wrote
>
>
> I've looked for some more information in the camel-users forum and I've
> found the following:
> http://camel.465427.n5.nabble.com/Bean-component-BeanInfo-thread-safety-td3387197.html
>
>
Also the changes of the MethodInfo class in CAMEL
cgiera wrote
>
> Hello,
>
> one of our customers has serious problems with our software which uses
> camel 2.6.0.
> Our cxf-Route throws a ClassCastException
>
> The route looks like this:
>
> from("cxf:bean:endpoint")
>
82 matches
Mail list logo