Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Hi, Ok, I understand, makes sense Thx again! Regards, /Tom > On 10 Jan 2020, at 20:08, Romain Manni-Bucau wrote: > > Activemq all shades all classes in a fatjar, it does not support camel 3, > use other activemq dependencied - client, broker for example. > >> Le ven. 10 janv. 2020 à

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Romain Manni-Bucau
Activemq all shades all classes in a fatjar, it does not support camel 3, use other activemq dependencied - client, broker for example. Le ven. 10 janv. 2020 à 19:40, Tom Coudyzer a écrit : > Got it working now by adding the following dependency > > > org.apache.httpcomponents > httpclient

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Got it working now by adding the following dependency org.apache.httpcomponents httpclient 4.5.3 So i the end the problem got solved by 1. Removing the ActiveMQ dependency 2. Adding the Apache HTTP component Wondering why it was not working with ActiveMQ enabled. Thanks everyone for

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Hi, thanks for keeps this going ! This is what I get ProtectionDomain (file:/C:/Users/johndoe/.m2/repository/org/apache/activemq/activemq-all/5.15.10/activemq-all-5.15.10.jar ) jdk.internal.loader.ClassLoaders$AppClassLoader@277050dc java.security.Permissions@3d51f06e (

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Romain Manni-Bucau
Hmm, can you log next the println DefaultManagementAgent.class.getProtectionDomain() to chck the source of this class? The line in the stack does not match sources. Do you have some camel eclipse plugin? Le ven. 10 janv. 2020 à 18:35, Tom Coudyzer a écrit : > This is the output of the classpath

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
This is the output of the classpath from the Junit test class, seems valid to me; unless i have overlooked something java.class.path c:\GIT\sandbox\com.xyz.camel.samples\camel.samples\camel.samples.apiLib\target\test-classes

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Tried to build now via the IDE and via the command line but both give the same result On Fri, Jan 10, 2020 at 5:41 PM Omar Al-Safi wrote: > Something else, do you build it from your IDE or through maven command > line? Not sure what else could be though > > On Fri, Jan 10, 2020 at 5:34 PM

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
I build it through the Eclipse IDE Regards, /Tom On Fri, Jan 10, 2020 at 5:41 PM Omar Al-Safi wrote: > Something else, do you build it from your IDE or through maven command > line? Not sure what else could be though > > On Fri, Jan 10, 2020 at 5:34 PM Romain Manni-Bucau > wrote: > > > Maybe

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Hi, Will override the setUp to check the classpath. Sharing will be difficult as it the API is not mocked up now. I will however create a mock API server if it's still not working. Thanks for all the help so far, you've been great! Regards, /Tom On Fri, Jan 10, 2020 at 5:34 PM Romain

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Omar Al-Safi
Something else, do you build it from your IDE or through maven command line? Not sure what else could be though On Fri, Jan 10, 2020 at 5:34 PM Romain Manni-Bucau wrote: > Maybe override setUp method with > > > System.out.println("java.class.path"); > super.setUp(); > > To ensure you run what

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Romain Manni-Bucau
Maybe override setUp method with System.out.println("java.class.path"); super.setUp(); To ensure you run what you think and that eclipse uses an up to date dependencies model. Le ven. 10 janv. 2020 à 17:31, Francois Papon a écrit : > Any chances to share your project? > > I can try to

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Francois Papon
Any chances to share your project? I can try to reproduce. regards, François fpa...@apache.org Le 10/01/2020 à 17:26, Tom Coudyzer a écrit : > Thanks, got the 3.1.0-SNAPSHOTS libraries now on the classpath but still > the same issue. > > On Fri, Jan 10, 2020 at 4:23 PM Andrea Cosentino wrote:

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Thanks, got the 3.1.0-SNAPSHOTS libraries now on the classpath but still the same issue. On Fri, Jan 10, 2020 at 4:23 PM Andrea Cosentino wrote: > The snapshot repository is > > https://repository.apache.org/snapshots/ > > You can also try to build Camel locally. > > Il giorno ven 10 gen 2020

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Andrea Cosentino
The snapshot repository is https://repository.apache.org/snapshots/ You can also try to build Camel locally. Il giorno ven 10 gen 2020 alle ore 16:21 Tom Coudyzer ha scritto: > Hi, > > Sorry but, what is the plugin repository for getting access to the SNAPSHOT > via Maven, guess it's not

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Hi, Sorry but, what is the plugin repository for getting access to the SNAPSHOT via Maven, guess it's not available from mvnrepository.com? Thank you. Regards /Tom On Fri, Jan 10, 2020 at 4:08 PM Francois Papon wrote: > Hi, > > Can you try with the 3.1.0-SNAPSHOT and the -U maven option? > >

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Francois Papon
Hi, Can you try with the 3.1.0-SNAPSHOT and the -U maven option? regards, François fpa...@apache.org Le 10/01/2020 à 16:02, Tom Coudyzer a écrit : > Hi, > > Still no luck. Changed it to camel-core-engine and cleared the Maven cache > after that. > > This is the code I'm testing (route + JUnit

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Hi, Still no luck. Changed it to camel-core-engine and cleared the Maven cache after that. This is the code I'm testing (route + JUnit test) Test = import java.util.HashMap; import org.apache.camel.builder.RouteBuilder; import org.apache.camel.test.junit4.CamelTestSupport; import

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Andrea Cosentino
Change camel-core to camel-core-engine. Il giorno ven 10 gen 2020 alle ore 15:48 Tom Coudyzer ha scritto: > Hi, > > This is the POM > > http://maven.apache.org/POM/4.0.0; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Hi, This is the POM http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;> 4.0.0 com.xyz camel.samples 0.0.1-SNAPSHOT pom UTF-8 11 11 3.0.0 1.7.29 5.15.10

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Andrea Cosentino
Also can you please show your code? Thanks. Il giorno ven 10 gen 2020 alle ore 15:36 Andrea Cosentino ha scritto: > What is your POM? > --Andrea Cosentino --Apache Camel PMC > ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: >

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Andrea Cosentino
What is your POM?  --Andrea Cosentino --Apache Camel PMC ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd On Friday, January 10, 2020, 3:34:04 PM GMT+1, Tom Coudyzer wrote: Thanks Omar

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Thanks Omar for the reply. Cleared the cache unfortunately still no luck, so there must still be something hanging around... Regards, /Tom On Fri, Jan 10, 2020 at 3:13 PM Omar Al-Safi wrote: > Hi, > > Java 8 should work at the moment. However, at some point in upcoming > versions of 3.x, I

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Omar Al-Safi
Hi, Java 8 should work at the moment. However, at some point in upcoming versions of 3.x, I think Java 8 support will be dropped. Referring to your error, looks like your depencides cache are not updated to camel 3.0, this method only exists in 2.14,x but not in 3.0. You can try to remove the

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Romain Manni-Bucau
Hi Did you check you classpath for an older camel dependency somewhere? Le ven. 10 janv. 2020 à 15:01, Tom Coudyzer a écrit : > Hi, > > Thanks for the reply. Switched to Java 11 (and as told earlier) checked the > migration guide, but still not working... > > Any other ideas? > > Thanks a

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Hi, Thanks for the reply. Switched to Java 11 (and as told earlier) checked the migration guide, but still not working... Any other ideas? Thanks a lot!! Regards, /Tom On Fri, Jan 10, 2020 at 2:52 PM Jeremy Ross wrote: > Camel 3 requires Java 11, or will soon. > > Also, make sure you've

Re: Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Jeremy Ross
Camel 3 requires Java 11, or will soon. Also, make sure you've made necessary changes outlined here https://camel.apache.org/manual/latest/camel-3-migration-guide.html. On Fri, Jan 10, 2020 at 7:49 AM Tom Coudyzer wrote: > Hi, > > Probably a stupid question but seems can't find a solution. I

Stack trace after upgrading to Camel 3.0

2020-01-10 Thread Tom Coudyzer
Hi, Probably a stupid question but seems can't find a solution. I upgraded to Camel 3.0 When I run now my test classes (using CamelTestSupport) I get the stacktrace below (Note atm still using Java 8) Any idea what the reason could be? Couldn't find either anything in the migration guide in