Sorry for the long delay, I got pulled onto another problem and am just
getting back to this issue.
@Jakub,
The problem I'm encountering is upon aggregation, the file aggregation
either times out or is stuck in a wait pattern until all multiplex routes
have completed. I can see in the logs whe
Claus, thank you for responding. I think you know i meant EndpointRegistry.
--
View this message in context:
http://camel.465427.n5.nabble.com/Create-endpoints-in-java-to-use-in-xml-routes-tp5775092p5775190.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Claus,
Thank you very much for the quick response which makes a lot of sense. But
how can I mark the original exception (1st error) as "handled" to prevent
the exchange from being processed again and again.
Thanks,
John
--
View this message in context:
http://camel.465427.n5.nabble.com/Direc
We love contributions, so you are much welcome to dive in the code to
see if that sourcePort can be added.
http://camel.apache.org/contributing
On Mon, Dec 14, 2015 at 11:36 PM, SteveR wrote:
> I'm currently facing a show-stopping production issue: I'm unable to figure
> out how to specify the U
That is by design to not handle errors while handling errors, eg you
can easily get in endless looping. When that happens Camel detect it
and does a fatal fallback error handling where the 2nd error is
logged.
On Wed, Dec 16, 2015 at 6:08 PM, bocamel wrote:
> I have the following context level O
- I have a Camel input route whereby camel-netty4 creates/binds a UDP socket
that listens on port 12345:
*from("netty4:udp://host:12345? ...)
.to("SEDA_QUEUE1" ...);*
- The input route receives a UDP datagram, creates the exchange, and sends
it to *SEDA_QUEUE1*.
- Then the exchange
I have the following context level OnException. After it catches an error,
it would send out an email alert using a direct-vm route. But to avoid
infinite loop, the email alert is only sent if the OnException is not
entered due to a nested exception.
When the direct-vm consumer is not started an
No that is not possible. There is a JIRA ticket to improve this in the
future. Its not an easy change.
On Wed, Dec 16, 2015 at 5:38 PM, mtkilbay wrote:
> My question may not have been clear enough so let me ask a specific question:
>
> Does anyone know whether i can use the EndpointRepository t
My question may not have been clear enough so let me ask a specific question:
Does anyone know whether i can use the EndpointRepository to add an endpoint
with a reference name, e.g., "kafkatopic" that i can then refer to in my xml
route like below:
Thanks.
--
View this message in context:
h
Okay found a mistake in the cxf namespace parser - and added a fix for
correct setter on the endpoint.
Nobody really use that service factory as camel sets one out of the box.
On Wed, Dec 16, 2015 at 3:58 PM, Joseph Kampf wrote:
> BTW,
>
> You should also consider removing the serviceFactory ele
Headers are already interpolated like :#headerName. I've never tried using
expressions in SQL like that.
On 15 December 2015 at 13:44, Shiv wrote:
> Hi,
> I want to insert a record in table using camel sql component and want to
> externalize the insert query in a properties file. Seems it is not
How much cleaner is the Groovy DSL compared to using Java 8 with the Java
DSL?
On 16 December 2015 at 02:10, souciance
wrote:
> I wouldn't mind using it but considering that most of the books and
> documentation is using the java or blueprint dsl so that makes it a bit
> easier.
>
>
>
> --
> Vie
BTW,
You should also consider removing the serviceFactory element from the XSD.
That is also misleading.
Joe
On 12/16/15, 9:29 AM, "Claus Ibsen" wrote:
>That was a mistake in the camel cxf documentation - i am removing
>that. Also that other xml file is not in use in an unit test and its
So I am having an issue getting the right Service Factory.
Clearing out the karaf/data/cache directory and then doing a fresh deploy of
the Bundle works fine.
However after restarting Karaf the org.apache.cxf.jaxws.JaxWsServerFactoryBean
is not used by the CxfEndpoint. Instead the
org.apach
That was a mistake in the camel cxf documentation - i am removing
that. Also that other xml file is not in use in an unit test and its
being removed as well.
You dont need to set that service factory when using camel-cxf. Just
remove it from your code.
On Wed, Dec 16, 2015 at 1:21 PM, Joseph Ka
Hi community,
This current project use JPA based idempotent repository and have exception:
[Camel (camel-1) thread #0 -] WARN
org.apache.camel.component.file.FileConsumer - Consumer
Consumer[file://D:%5C1?idempotent=true&idempotentRepository=%23jpaStore]
failed polling endpoint:
Endpoint[file://D
I found the Error!
All cases must be lower!
so this work:
getOutFilter().add("messagehistory");
This don't work:
getOutFilter().add("MessageHistory");
--
View this message in context:
http://camel.465427.n5.nabble.com/Add-my-own-Filter-on-http4-tp5775147p5775152.html
Sent from the Camel - Us
I am trying to specify the ServiceFactory used by my CXF Endpoint.
However I am getting the following error:
karaf@root()> Exception in thread "SpringOsgiExtenderThread-50"
org.apache.camel.RuntimeCamelException:
org.apache.camel.FailedToCreateRouteException: Failed to create route
Hello together,
i want to use a own headerFilterStrategy on my own Component extends from
http4.
So I create this class:
public class DefaultHeaderFilterStrategy extends HttpHeaderFilterStrategy {
public DefaultHeaderFilterStrategy() {
super();
get
Hi,
I found the anwer to the problem in apache cxf forums.
http://cxf.547215.n5.nabble.com/How-to-increase-the-max-size-of-a-REST-response-td563077.html
This is more of a issue in the CXF component than camel. But still for
referene, i am sharing this information.
At the server side, we saw t
I am trying to use the option /deadLetterHandleNewException(false)/ in order
to have any new Exception occurring during the dead letter processing be
propagated back. Unfortunately, when doing so, it seems that the dead letter
channel propagates back the original exception as well, even if the
Dead
In general I would say integration is usually event-based and hopefully
asynchronous. It makes everything much easier to handle.
In your case it is batch oriented and you need to take action afterwards.
I am sure it can be achieved in Camel and you'd probably have to write
several customised code
I wouldn't mind using it but considering that most of the books and
documentation is using the java or blueprint dsl so that makes it a bit
easier.
--
View this message in context:
http://camel.465427.n5.nabble.com/java-dsl-vs-blueprint-xml-tp5775085p5775124.html
Sent from the Camel - Users mai
23 matches
Mail list logo
