Re: Does Camel JPA component implement it's own connection pooling?

Can you share us your camel route? It is important for us to find out the key reason of your issue. 发自我的 iPhone 在 2013-1-26，上午5:22，Chris Wolf 写道： > On Fri, Jan 25, 2013 at 3:55 PM, Chris Wolf wrote: >> I ask because when I use jpa: in producer mode, I get this error: >> Caused by: oracle.

Re: Custom interceptors and finding the first and last camel route

I don`t understand what you are asking. Usually you can just add a ".to(somethingElse)" at the end of your route. Or you can add some http://camel.apache.org/predicate.html to check if your request was succesful first. If your 2 routes should be in sync, why aren`t they on the same route ? Else y

Endpoint Uri not recognized but functional, possible bug.

Hello, Using camel 2.10.3 Here is the test case : http://pastie.org/5865294 Both test are success, but it doesn`t seem right. Both Endpoint are used and working but I can`t get it back from the CamelContext if I don`t add it directly to the CamelContext. Thanks for your time. -- View this me

Re: CXF endpoint and properties

Hi, I am using 2.10.1. Is it possible to you spring place holders? something like http://camel.465427.n5.nabble.com/CXF-endpoint-and-properties-tp4848384p5726303.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Does Camel JPA component implement it's own connection pooling?

On Fri, Jan 25, 2013 at 3:55 PM, Chris Wolf wrote: > I ask because when I use jpa: in producer mode, I get this error: > Caused by: oracle.net.ns.NetException: Listener refused the connection > with the following error: > ORA-12519, TNS:no appropriate service handler found > > Strangely, using j

Does Camel JPA component implement it's own connection pooling?

I ask because when I use jpa: in producer mode, I get this error: Caused by: oracle.net.ns.NetException: Listener refused the connection with the following error: ORA-12519, TNS:no appropriate service handler found Strangely, using jpa: in consumer mode, this does not happen. In the tnslsnr.log

Re: HL7 Mina throwing org.apache.mina.filter.codec.ProtocolDecoderException: org.apache.mina.common.BufferDataException

We're working in asynchronous mode where they send all of the messages and I send the response back as each one is processed using ActveMQ for JMS queuing. It worked fine in my own testing but is failing here. What I don't understand is the length of the message: 189616968 bytes The hex for the m

Re: HL7 Mina throwing org.apache.mina.filter.codec.ProtocolDecoderException: org.apache.mina.common.BufferDataException

189616968 bytes may be simply too much... The normal ("original") mode of operation in HL7 is to send one message, receive the response, send the next message, receive the next response and so on. Much like HTTP, however, instead of defining the length of a request somewhere, MLLP delimits a reque

Re: NullpointerException in ClassPathXmlApplicationContext

Hi Claus and Christian, thanks for your support. Using JAXB 2.2.6 helped it out. But I will also check for a newer JDK version. Kind regards, Christian -Ursprüngliche Mitteilung- Von: Claus Ibsen-2 [via Camel] An: Christian Jacob Verschickt: Fr, 25 Jan 2013 7:42 am Betreff: Re: N

HL7 Mina throwing org.apache.mina.filter.codec.ProtocolDecoderException: org.apache.mina.common.BufferDataException

I'm getting the exception below when using the HL7 component and codec with mina to receive streamed HL7 messages. The program works find when I send it separate messages from a 2nd program using Camel/HL7/Mina and receives an ACK successfully. But when testing with our client we're seeing this

Dynamically building endpoint

I have a bean, lets call it "b" and a property P on the exchange. I want to send the exchange to an endpoint with the URI: "foo:" + b.getSomeValue(getProperty(P)) + ":bar:" + b.getSomeOtherValue(getProperty(P)) + ":suffix" Is it possible to do this using to(...) or toF(...) ? If so, what would

Camel Quartz Bug

Friends, I think there´s a bug in camel-quartz component. When I start 500 camel quartz routes I have 500 triggers fired. When I start 600 camel quartz routes I have 600 triggers fired. When I start 700 camel quartz routes I have 700 triggers fired. When I start 800 camel quartz routes I have 800

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

FWIW, I think I first mentioned hawtio in the Camel 3.0 thread (message from 8:27 am) when you asked Lukasz to look at the lightweight web console, only saying we should look at it. James started this different thread to actually not pollute the Camel 3 discussion with hawtio details. So I think

Re: Scala DSL with Scala 2.10

> Totally agree. The Scala way to do is to build and publish camel-scala_2.9.2- > 2.11.0.jar and camel-scala_2.10-2.11.0.jar I reopened the Scala 2.10 issue [1] so we might settle an agreement on how Scala backwards compatibility should be handled in Camel. +1 for renaming existing Scala module t

Re: Persisting route details..

Camel currently is essentially stateless. You can achieve what you want, but you'd have to implement it yourself. Something along the lines you mentioned. We are however planning to have support for persistence at a core level in 3.0. Christian Ohr added some details about that on the 3.0 idea

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

Ok, that is a different discussion I would rather have in the context of Camel 3.0. I will start a separate thread for this. Having the conversation in the context of the subject of this thread may be confusing. Sorry for the misunderstanding. Cheers, Hadrian On 01/25/2013 10:42 AM, Guillaum

Persisting route details..

Hi, There are a couple of use-cases that I want to address - 1. Persisting all routes last start-time and end-time somehow so that on the application server startup routes do not start if they have just recently ran and also to report route statistics. 2.Modifying the routes such that the change

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

You misunderstood me. So I rephrase. Camel and ActiveMQ community needs a versatile console which can run in a non OSGi environement, so they can't drop their current web console in favor of the karaf one. This discussion is imho totally relevant for the camel community, as it is for all other p

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

This is one more reason why the hawt.io discussions should take place in the hawt.io communities. Not here. Thanks, Hadrian On 01/25/2013 08:08 AM, Guillaume Nodet wrote: Lukasz, I'm sorry you're angry, but you're missing the point that the Karaf web console is bound to OSGi even if it can be

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

I personally find the tone of this exchange very distasteful and I would much appreciate you continuing it on other media channels than the @camel user lists. FWIW, Lukasz made some valid points. However, you saw a need for a new project, created it, great. Hawt.io is nice, please continue to

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

On Fri, Jan 25, 2013 at 2:36 PM, Łukasz Dywicki wrote: > I'm not angry. I'm just telling the truth. Nobody told to you yet. Thx for that, I think I was really erring on the dark side before ;-) > Why you think it's bound to OSGi? We have WAR packaging. Overall > destination was always to su

Re: File component - run them sequentially

On Fri, Jan 25, 2013 at 3:38 PM, renamsavio wrote: > Does someone have any idea how to solve it? > You can use the API on CamelContext to start|stop routes. So you would need to figure out when there is no more files on route1, to start route2, and so forth. And what should happen when route 3 is

Overload CamelContextFactoryBean

Hi, does anybody knows a way to overload/extend the spring osgi implementation of CamelContextFactoryBean? I actually wants to extend the basic implementation to do some further magic. :-) There seems to be some tricky ways to do it with an own SpringNamespaceHandler and extending the camel-spr

Getting next JMS Message before Route is Suspended

I have read several posts on suspending routes such as http://camel.465427.n5.nabble.com/Suspend-route-what-about-the-current-exchange-td5545837.html and have read https://camel.apache.org/how-can-i-stop-a-route-from-a-route.html. The problem I am having is that in the time that it takes to spawn

Re: Camel Routing using Java DSL in Servlet without Spring

On Fri, Jan 25, 2013 at 10:46 AM, CamelNewbieUser wrote: > Hi, > > I tried to find release date for Apache Camel 2.11 but it is nowhere > mentioned. > Also the links provided on the site > > is showing HTTP 4

Re: Camel Routing using Java DSL in Servlet without Spring

On Fri, Jan 25, 2013 at 10:46 AM, CamelNewbieUser wrote: > Hi, > > I tried to find release date for Apache Camel 2.11 but it is nowhere > mentioned. > Also the links provided on the site > > is showing HTTP 4

Re: Scala DSL with Scala 2.10

Henryk Konsek writes: > > > I have logged ticket > > https://issues.apache.org/jira/browse/CAMEL-6011 > > > > And upgrading Scala now. > > Actually this is not a Scala-way to just upgrade the version of the library. > > In fact we should create separated module for 2.10 (cloned from the > 2.9)

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

I'm not angry. I'm just telling the truth. Nobody told to you yet. Why you think it's bound to OSGi? We have WAR packaging. Overall destination was always to support other runtimes. Charles was talking about that and he found even a name for it once it will get TLP (Orion). But it was so long ag

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

Lukasz, I'm sorry you're angry, but you're missing the point that the Karaf web console is bound to OSGi even if it can be reused with Camel or ActiveMQ. So the Camel and ActiveMQ community will never drop their own console, because the OSGi users is only a fraction of the user base. Hawtio enable

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

On 25 January 2013 12:58, Preben.Asmussen wrote: > Gave it a ride to test it and it looks awesome. > Thanks! > Still prefer VisualVM when it comes to monitoring though. Besides JMX > threads, CPU and mem can be accessed here too. Ye

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

Gave it a ride to test it and it looks awesome. Still prefer VisualVM when it comes to monitoring though. Besides JMX threads, CPU and mem can be accessed here too. More feedback to come later when I get some more time. /Preben

Multiple POST parameters in Spring DSL

Hello, I am currently facing issue with passing multiple POST parameters from html page to servlet and routed to Camel Spring DSL. POST applica

Re: Camel Routing using Java DSL in Servlet without Spring

Hi, I tried to find release date for Apache Camel 2.11 but it is nowhere mentioned. Also the links provided on the site is showing HTTP 404. I tried to download the SNAPSHOT version and build using Maven

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

On 25 January 2013 11:51, Łukasz Dywicki wrote: > Gentelmans, > Especially from Fuse. We have something similar already in Karaf repository > and it's called WebConsole. It been there since 2011. I'm sure you was aware > of that, especially Guilliaume. I'm aware of most of the consoles at Apach

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

Gentelmans, Especially from Fuse. We have something similar already in Karaf repository and it's called WebConsole. It been there since 2011. I'm sure you was aware of that, especially Guilliaume. There was example how to use it together with Camel and ServiceMix. But you never took time to take

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

If the feature file doesn't work you could just try this: * add this line to your etc/org.ops4j.pax.url.mvn.cfg (which won't be needed once we've released 1.0 soon ;) org.ops4j.pax.url.mvn.repositories= \ https://oss.sonatype.org/content/repositories/snapshots=sonatype.snapshot.repo \ * th

Re: [ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

Hello, it looks really nice…I just give it a try, trying to install it in Karaf, where is my Camel project running, but after ~50 minut I wasn't succesfull. I was trying to utilize Fuse features.xml, to install hawtio, but that wasn't probably good idea :) I'll come back to it later, but if there i

Eclipse Plugin & Production Build

i've got a question about building production releases when the content XML file is setup for the Eclipse. I have (in my POM) moved the 'camel-eclipse' plugin to a separate profile which i only reference in an Eclipse run configuration. The trouble is, however, that i therefore need a way to [condi

[ANN] hawtio: a new lightweight HTML5 console for Apache Camel, ActiveMQ, JMX, OSGi & Fuse Fabric

For the impatient just look here :) http://hawt.io/ Background == We've had numerous consoles all over the place for some time in various projects like Felix, Karaf, ActiveMQ, Camel, Tomcat, Fuse Fabric to name but a few. Many of them quite heavy weight requiring a custom web app to be dep

Re: HTTP4 Client + SSL + Accept All Hostnames + Accept All certificates

Hi, I need to do exactly the same as described in this topic, but it doesn't work for me, neither with camel 2.8.0 nor with the newer camel version 2.10.3 - I still get "javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated". Here is what I did: My own HttpClientConfigurer: public cl

Re: Scala DSL with Scala 2.10

> I have logged ticket > https://issues.apache.org/jira/browse/CAMEL-6011 > > And upgrading Scala now. Actually this is not a Scala-way to just upgrade the version of the library. In fact we should create separated module for 2.10 (cloned from the 2.9). New development should take place in 2.10 m