Re: i am getting exception org.apache.cxf.interceptor.Fault: org/apache/camel/CamelContext

actually i am using the apache-tomee-jaxrs as server. and i included this two library camel-core-2.12.1 camel-mail-2.12.1. so its work.try it. -- View this message in context: http://camel.465427.n5.nabble.com/i-am-getting-exception-org-apache-cxf-interceptor-Fault-org-apache-camel-CamelContext

Re: How does bean integration work in non-Spring contexts?

Is that what the element is for? Also, I'm looking for ways to use Camel that don't depend on Spring in order to maintain forward OSGi compatibility. Spring Boot et al. are practically the opposite of OSGi, so it doesn't seem like such a smart idea to use it when one intends on staying modular.

Re: No bean could be found in the registry for JNDI Look up using EJB Component

Hi and thanks for the quick response! Now it's working ok... as you point, the problem was that the ejb remote interfaces were not present in camel app. Thanks a lot! -- View this message in context: http://camel.465427.n5.nabble.com/No-bean-could-be-found-in-the-registry-for-JNDI-Look-up-usi

Re: How does bean integration work in non-Spring contexts?

Not true. @BeanInject, @PropertyInject etc. DO WORK in blueprint. I've used it. -Manav On Tue, Jul 15, 2014 at 3:51 PM, Charlie Mordant wrote: > I'm pretty sure annotations won't work with blueprint, but I think you can > use beanRef("myBean") camel Java dsl (sorry, I missed the annotation par

Re: How does bean integration work in non-Spring contexts?

I'm pretty sure annotations won't work with blueprint, but I think you can use beanRef("myBean") camel Java dsl (sorry, I missed the annotation part of the question). If you want to compare a bp vs a CDI versions of a camel module, here's a path to the same module made both ways: https://github.co

Re: How does bean integration work in non-Spring contexts?

Right, but does @BeanInject, @EndpointInject, etc., all work in Blueprint? Or do you still have to manually wire everything together in Blueprint? On 15 July 2014 14:38, Charlie Mordant wrote: > Hi Matt, > > camel-blueprint also makes blueprint beans working with camel. > > Regards, > > > 2014-

Re: How does bean integration work in non-Spring contexts?

Hi Matt, camel-blueprint also makes blueprint beans working with camel. Regards, 2014-07-15 20:09 GMT+02:00 Matt Sicker : > So I'm guessing in order for it to work in OSGi using services, it would > require a bit of additional code? > > I'll take a look at the CDI stuff, though, as we're consi

Re: weaveById - works with 2.13.1, not with 2.14-SNAPSHOT

FWIW, all tests pass in camel-core with this change reverted. [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 20:57 min [INFO] Finished at: 2014-0

Re: How does bean integration work in non-Spring contexts?

So I'm guessing in order for it to work in OSGi using services, it would require a bit of additional code? I'll take a look at the CDI stuff, though, as we're considering using it instead of Blueprint for our routes. On 15 July 2014 13:01, Claus Ibsen wrote: > Hi > > Yes these are Camel annota

Re: How does bean integration work in non-Spring contexts?

Hi Yes these are Camel annotations and there is some code in camel-core / camel-spring / camel-guice / camel-cdi to inject and support these annotations in those environments. Though camel-cdi is a bit special as its using some cdi extension and whatnot. And it could use a little cdi love to be i

Re: No bean could be found in the registry for JNDI Look up using EJB Component

Yes,The issue is resolved.Here is the action points might be helpful for you.-- Stubs should be present in your camel code(EJB remote interface)-- EJB component sd be registered with correct initial contextLet me know if this does not work and share your trace and code.Thanks, Dwiti -- View this

Re: Desktop applications

I also think this sounds like a good case for camel. Christian On 15.07.2014 18:42, Matt Sicker wrote: A fat rich client like that sounds like a good use case of Camel to me. On 15 July 2014 05:30, Jon Mithe wrote: -- Christian Schneider http://www.liquid-reality.de Open Source Archite

Re: weaveById - works with 2.13.1, not with 2.14-SNAPSHOT

If I revert the following change to AdviceWithTasks.java, it seems to solve this issue: https://github.com/apache/camel/commit/b08edf391bddb99078f15966394ac264440ffce9 I cloned master, reverted this change, then installed everything to test. On Jul 15, 2014, at 7:59 AM, Claus Ibsen wrote: >

Re: No bean could be found in the registry for JNDI Look up using EJB Component

Hi, I'm currently facing the same problem that you describes. Did you solve this issue? Thanks! -- View this message in context: http://camel.465427.n5.nabble.com/No-bean-could-be-found-in-the-registry-for-JNDI-Look-up-using-EJB-Component-tp5749335p5753882.html Sent from the Camel - Users mail

Re: Desktop applications

A fat rich client like that sounds like a good use case of Camel to me. On 15 July 2014 05:30, Jon Mithe wrote: > Thanks for all your help. > > The desktop apps I work on have connections to multiple back end servers > often though a single message broker, some generic protocols, some > proprie

How does bean integration work in non-Spring contexts?

Suppose I'm using CDI, or Blueprint, or Guice, or really anything other than Spring. The documentation < http://camel.apache.org/bean-integration.html> doesn't really explain how this works. Do things just work automatically? -- Matt Sicker

RE: Error handling in aggregation strategy

You can still throw exceptions by putting the exception in the exchange object. Exchange.setException(..); Elvio -Original Message- From: Richa [mailto:rsinha2...@gmail.com] Sent: 15 July 2014 15:40 To: users@camel.apache.org Subject: Error handling in aggregation strategy Hi, I have

Re: i am getting exception org.apache.cxf.interceptor.Fault: org/apache/camel/CamelContext

Hey Ishwar, Even i am using the eclipse. Which lib did you put into apache lib..?? -- View this message in context: http://camel.465427.n5.nabble.com/i-am-getting-exception-org-apache-cxf-interceptor-Fault-org-apache-camel-CamelContext-tp5742012p5753875.html Sent from the Camel - Users mailin

Error handling in aggregation strategy

Hi, I have a camel route having a custom aggregation strategy which extends AggregationStrategy. As per the signature of aggregate() method, it does not allow to throw an exception. But I want to handle the exceptions (that might occur in the aggregation strategy) in the base route builder in the

Re: weaveById - works with 2.13.1, not with 2.14-SNAPSHOT

On Tue, Jul 15, 2014 at 3:56 PM, Matt Raible wrote: > It tried it with 2.13.2 and it works just fine. > Thanks. If its possible for you then you are welcome to .zip an unit test / sample project that has this issue and create a JIRA ticket and attach it, or some github repo or something else. I

Re: weaveById - works with 2.13.1, not with 2.14-SNAPSHOT

It tried it with 2.13.2 and it works just fine. On Tue, Jul 15, 2014 at 12:12 AM, Claus Ibsen wrote: > Hi > > Can you try with 2.13.2 also? > > There was a fix in this to fix an issue when using Content Based > Router and weaveById. I bet it may has cause a regression for your > use-case. > > O

Re: How to expose camel producer with jmx

Thanks but what this means exactly (""as part of a" send processor mbean under the processor folder")? I have many "processors" with prefix "to", "unmarshal", "process", "multicast" and "log". I guess my producer should be found under "to", right? I clicked through all "to" processor and on firs

Using xpath inside an exchange

Hi everyone ! I'm still new to camel and I'm trying to use the enrich methode and the aggregation strategy. What's I'm trying to do is merging 2 xml files that look alike, like *this* : 12 2 and *that* : 14

Re: How to expose camel producer with jmx

Hi Producers are not enlisted in JMX - only endpoints and consumers. This is due to historical reasons, back then to not cause OOME by enlist too many mbeans. Usually a producer used by a route gets enlisted "as part of a" send processor mbean under the processor folder. I think there is a ticke

Re: Camel ftp consumer ignores idempotent file repository on start

Thanks again Claus, it's not the first issue i've got on using java to set things up. I think the documentation should consequently use java on java examples and not mix it up with uri-based setup (not compiler checked, error prone). In my case i have to set up routes based on very simple propert

Re: Camel ftp consumer ignores idempotent file repository on start

Hi If you mean http://camel.apache.org/idempotent-consumer.html Then thats an EIP and its not 100% the same. As the file/ftp component has idempotent out of the box. This allows those to know earlier if a file has been consumed before or not, and then not even attempt to consume the file. The EI

Re: Dynamic Endpoint URI - jetty producer's too many threads - Request parameter as part of the URL

Hi Yeah see this too http://camel.apache.org/how-to-remove-the-http-protocol-headers-in-the-camel-message.html On Tue, Jul 15, 2014 at 11:28 AM, vadimiron wrote: > No - my last message was wrong - this simple route is working now. > > I think i must remove all possible headers (Camel*, Host etc.

How to remove intercept() or process()

I want to remove intercept or process from superclass in test. camel: 2.13.1 output: java.lang.IllegalArgumentException: There are no outputs which matches: InterceptId in the route: direct:in It's WebService writing in Spring. Camel Context is defined in .xml, routes in Java DSL. In this case

How to expose camel producer with jmx

same as here: http://stackoverflow.com/questions/24755796/how-to-expose-camel-producer-with-jmx (if you want points ;-)) I read the documentation about camel jmx. In my case i want to expose some attributes and operations of a Producer (made a custom component). There seems to be no example for jm

Re: Camel ftp consumer ignores idempotent file repository on start

Thanks for this hint! This should be mentioned in docs. In my case i didn't saw this log entry but i saw a log entry for each file name being added to repository - so i didn't came to the idea that repository must be started. Now i am working with ".idempotentConsumer(header("CamelFileName"), fileR

Re: Desktop applications

Thanks for all your help. The desktop apps I work on have connections to multiple back end servers often though a single message broker, some generic protocols, some proprietary and essentially it aggregates across all of them all, plenty of processing / transforming and essentially providing data

About acquiring endpoints and using setters on them

I just stumbled across a problem: https://issues.apache.org/jira/browse/CAMEL-7599 (i created it) It took me hours to figure out that setters on an endpoint acquired like this LogEndpoint endpoint = context.getEndpoint("log:tplogger", LogEndpoint.class); won't work a call of endpoint.setGroupSize

Re: Dynamic Endpoint URI - jetty producer's too many threads - Request parameter as part of the URL

No - my last message was wrong - this simple route is working now. I think i must remove all possible headers (Camel*, Host etc.) after other HTTP requests, that are executed before my request -- View this message in context: http://camel.465427.n5.nabble.com/Dynamic-Endpoint-URI-jetty-produce

Re: Dynamic Endpoint URI - jetty producer's too many threads - Request parameter as part of the URL

Some more information: as starting point of our route we have a jetty server from("jetty:http://0.0.0.0:8080/myservice?httpClient.idleTimeout=3&httpClient.soTimeout=3";) .setHeader(Exchange.HTTP_URI, simple("http://172.29.15.37/service/lala";)) .to("http://localhost";) That the whole rou

Re: Throughput logger logs every message - how to configure properly?

This is beeing fixed in 2.14: https://issues.apache.org/jira/browse/CAMEL-7599 Thanks for that! -- View this message in context: http://camel.465427.n5.nabble.com/Throughput-logger-logs-every-message-how-to-configure-properly-tp5753784p5753827.html Sent from the Camel - Users mailing list arc

Re: Dynamic Endpoint URI - jetty producer's too many threads - Request parameter as part of the URL

Check unit tests of camel-jetty / camel-http for samples. On Tue, Jul 15, 2014 at 11:09 AM, vadimiron wrote: > That doesn't help - i have already rewritten my route to: > .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.GET)) > .setHeader("CamelHttpUri", > simple("http://localhost/myservice/

Re: Dynamic Endpoint URI - jetty producer's too many threads - Request parameter as part of the URL

That doesn't help - i have already rewritten my route to: .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.GET)) .setHeader("CamelHttpUri", simple("http://localhost/myservice/${header.myparam}";)) .to("http://dummyhost";) but the request goes always to dummyhost. What else can i check? Befo

Re: Dynamic Endpoint URI - jetty producer's too many threads - Request parameter as part of the URL

Turn off bridgeEndpoint On Tue, Jul 15, 2014 at 10:30 AM, vadimiron wrote: > Does it work with the jetty http client? > > This doesn't work - URI is not rewritte > > .setHeader("CamelHttpUri", simple("http://localhost/myservice/${myparam}";)) > .to("jetty:dummy?bridgeEndpoint=true&httpClient.soTi

Re: Dynamic Endpoint URI - jetty producer's too many threads - Request parameter as part of the URL

Does it work with the jetty http client? This doesn't work - URI is not rewritte .setHeader("CamelHttpUri", simple("http://localhost/myservice/${myparam}";)) .to("jetty:dummy?bridgeEndpoint=true&httpClient.soTimeout=15000&httpClient.timeout=3&httpClient.connectTimeout=5000") The tracer shows

Re: Running apache camel ftp example

Sometimes stupid questions are the main points ;) Thanks a lot=) -- View this message in context: http://camel.465427.n5.nabble.com/Running-apache-camel-ftp-example-tp5753782p5753821.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Dynamic Endpoint URI - jetty producer's too many threads - Request parameter as part of the URL

Hi Do not use recipient list, but a single endpoint. And use a header with the dynamic http url or query parameters to use. Those headers is documented at http://camel.apache.org/http On Tue, Jul 15, 2014 at 9:28 AM, vadimiron wrote: > We have some external service - the requests to this service

Dynamic Endpoint URI - jetty producer's too many threads - Request parameter as part of the URL

We have some external service - the requests to this service are sent from our camel route with jetty client (producer). The url of this service is the following - http://host/some/service/methodname/id id is dynamic - it is some parameter, that is different in each request. .to("endpoint_uri") op

Re: Desktop applications

A UI and camel will only very rarely be a good match. So the first thing you should check is if you really need camel. Often you only need an eventing mechanism. One of the best methods to check for this is to try to implement something with camel and with pure java. If the java solution is only