Hi Aki,
it was not working initially because I tried to use the WSDL for namespace A.
CXF could not process the message because it was transformed to namespace B too
early.
For the second point, the situation is like this:
we have old clients and old services that exchanged messages in namespa
Hi
What do you mean by "log throttled messages"? Do you want for example
to know if a message was hold back by the throttler or not? Or do you
want the throttler to do some kind of logging if it holds back a
message and how would you configure that in camel ?
On Wed, Jan 21, 2015 at 11:49 PM, Ant
Hi, I've written a JUnit test in Eclipse for a Camel route.
It has been working fine for days, but now it doesn't startup failing in the
CamelTestSupport.setUp method:
I've tried to cleanup the Maven repository especially the camel-core,
camel-test and junit repositories.
When I right-click on t
Hi, I've written a JUnit test in Eclipse for a Camel route.
It has been working fine for days, but now it doesn't startup failing in the
CamelTestSupport.setUp method:
I've tried to cleanup the Maven repository especially the camel-core,
camel-test and junit repositories.
When I right-click on t
Hi
Yeah sounds strange as they are both from the very same jar - camel-core.
btw you do not need to type cast you can use the api on camel context.
which we may consider removing the @deprecation as its more annoying than good.
And instead of type cast we should add an adapt(T) method for ppl to
I am not type casting myself.
The cast is inside the class CamelTestSupport:
All I'm doing is overriding the createCamelContext, which I've done
succesfully in the past:
Do you know if the DefaultCamelContext in a previous version of Camel didn't
implement the interface ModelCamelContext?
Maybe
Hi
Yeah such kind of errors can often be about mixed versions of a
library on the class path etc. So I would double check that you only
use same version of Camel.
If you use maven then check the pom.xml
On Thu, Jan 22, 2015 at 1:19 PM, geppo wrote:
> I am not type casting myself.
> The cast is
Found the problem, my project is using Camel 2.9.3, but it has a dependency
on another project which uses Camel 2.8.0 and for whatever reason the lower
version jar is the one loaded by Eclipse when running the test.
Thanks for your help!
--
View this message in context:
http://camel.465427.n5.n
Hi all,
I'm a newbie about Camel.
For my first post is a simple request.
Is it possible for new html versions of camel-manual a more readable font?
I saw the previous pdf versions and they're perfect.
Thanks.
Regards,
Andrea Barisone
--
View this message in context:
http://camel.465427.n5.nab
Hello,
A quick update to this. Would the camel approach to managing Quartz jobs
programmatically be:
1.For every new job, create a new route dynamically. The quartz endpoint
would be configured dynamically by creating the option string programmatically.
Something like this:
a.
from("
Camel - provides users java code free environment , it has various components
to fulfill users requirement.
The best way is to use XQuey?XSLT to form INBOUND / OUTBOUND messages.
While XQuery can be used for simple transformations, it lacks the power and
sofistication of XSLT (especially template
Hi
I would only suggest xslt if you have experience using it and are
comfortable using it. It can be really hard to understand and maintain
if it gets big.
Plain java code, even if its doing boiler plate get -> set is
something everybody understands and can maintain.
And there is some libraries
I've added an example showing how to upload a document to a content
workspace:
http://camel.apache.org/salesforce.html
Does anybody else have any useful examples they could share for this
component?
Hi Claus,
I'm attaching a handler which it seems like it fixes the issue for us.
I think the documentation should clarify that the requestTimeout
parameter in the netty component is not per request but a actually a
netty channel readTimeout.
regards
--
joan
* Claus Ibsen [20150117 12:02]:
> Hi
I'm successfully using REST DSL to serve up some simple services and
want to include some simple HTML docs to describe and illustrate the
services provided and prefer to keep this as
simple as possible.
I just have a process started by a Main class that starts a camel
context with some routes e
2015-01-22 10:07 GMT+01:00 Dirk Lattermann - expertplace
:
> Hi Aki,
>
> it was not working initially because I tried to use the WSDL for namespace A.
> CXF could not process the message because it was transformed to namespace B
> too early.
okay. That means, it didn't even get to the out chain.
Hi,
I'm trying to use camel-lucene component to crawl data from an existing
lucene index.
What is the best way to crawl data from Lucene index in batches?
For example:
- Lucene Index has 100,000 documents
- I want to query/read 1000 documents at a time and process them.
- Seems the current camel-
On Fri, Jan 23, 2015 at 12:30 AM, Claus Ibsen wrote:
> What do you mean by "log throttled messages"? Do you want for example
> to know if a message was hold back by the throttler or not? Or do you
> want the throttler to do some kind of logging if it holds back a
> message and how would you confi
On Fri, Jan 23, 2015 at 6:58 AM, Tim Dudgeon wrote:
> I'm successfully using REST DSL to serve up some simple services and want
> to include some simple HTML docs to describe and illustrate the services
> provided and prefer to keep this as
> simple as possible.
> I just have a process started by
Hi,
I am looking to integrate use Camel Rest DSL on a IBM Websphere instance.
All the servlets are mapped to http://host/services. How can I configure the
rest dsl for the ibm configuration?
Thanks,
Ali
-
Alireza Salemi
--
View this message in context:
http://camel.465427.n5.nabble.com/C
There is a post in oracle community on the same topic :
https://community.oracle.com/thread/2144048
So it also depends on what is the type(complexity,xml size,% of
transformation in an xml,..) of transformation that you are using and also
whether you prefer better+easy maintenance over slight diff
Hi Aki, please see below.
> -Ursprüngliche Nachricht-
> Von: Aki Yoshida [mailto:elak...@gmail.com]
> Gesendet: Donnerstag, 22. Januar 2015 22:04
> An: users@camel.apache.org
> Betreff: Re: Camel-CXF: Problems transforming namespace of incoming
> message
>
> 2015-01-22 10:07 GMT+01:00 Dir
22 matches
Mail list logo
