Hello
Camel 2.9.2, CXF 2.6.0
I am trying to run a Camel CXF consumer route using the following endpoint
definition:
http://localhost:9003/Utility/TestLogWS";
wsdlURL="META-INF/wsdl/Utility/TestLogWS.wsdl"/>
I have the following dependency
org.slf4j
slf4j-log4j12
1.5.11
Hi
You need to use slfj4 1.6 onwards.
On Sat, May 12, 2012 at 9:45 AM, Fitzcaraldo
wrote:
> Hello
>
> Camel 2.9.2, CXF 2.6.0
>
> I am trying to run a Camel CXF consumer route using the following endpoint
> definition:
>
> address="http://localhost:9003/Utility/TestLogWS";
> wsdlURL="META-
On Fri, May 11, 2012 at 6:05 PM, Rocco Gallo Citera
wrote:
> Thank you Claus, I read both before sending the mail.
> I will try to explain myself better.
> I do not understand why, with load balancing between two HTTP nodes,
> if I have a client route starting with a timer with certain
> configura
If you add attachclasses to the maven war plugin you can use the classifier
classes to get them as dependency normally.
Well, ill probably look soon but i think ill simply make this path(s)
configurable.
- Romain
Le 11 mai 2012 21:06, "Nestor Urquiza" a écrit :
> The war as dependency won't wor
Thanks Claus
Updated slf4j dependency to 1.6.4
org.slf4j
slf4j-log4j12
1.6.4
test
This resulted in this at runtime:
SLF4J: The requested version 1.6 by your slf4j binding is not compatible
with [1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.5.9, 1.5.10, 1.
Hi
Double check that you only have slfj4 1.6 JARs on your classpath
You can run
mvn dependency:tree
On Sat, May 12, 2012 at 11:53 AM, Fitzcaraldo
wrote:
> Thanks Claus
>
> Updated slf4j dependency to 1.6.4
>
>
> org.slf4j
> slf4j-log4j12
> 1.6.4
> test
>
>
> This resulted in thi
Whenever you are done I will test. I guess your proposal is to have something
like ${basedir}/target/classes
Thanks for following up on this.
--
View this message in context:
http://camel.465427.n5.nabble.com/diagram-generator-tp4375588p5707039.html
Sent from the Camel - Users mailing list archi
The problem was AMQ 5.5.1 which was pulling in the earlier version of slf4j.
Upgraded to AMQ 5.6.0 and all good.
Thanks Claus.
--
View this message in context:
http://camel.465427.n5.nabble.com/slf4j-and-jetty-tp5706803p5707863.html
Sent from the Camel - Users mailing list archive at Nabble.com.
For those who hit this.
I updated a simple Camel JMS route to use AMQ 5.6.0.
The ConnectionFactory is specified in camel.context as follows:
The route now failed with ClassNotFound for PooledConnectionFactory.
I needed to add a dependency on activemq-pool which is no longer pulled
