Hi Glad you got it working. Learning Camel is very mich learn by doing, as its so quick to get running that most people jump in right away. No need to read a 200 pages .pdf to start ;)
So please continue to post questions or issues, that is why we have this vibrant community to help. These 'errors' is logged at DEBUG level while Camel is loading the type converters based on classpath scanning the .jars. You can basically ignore this, or if you want to remedy it, you can add or remove needed .jars. For instance you have this -test jar on the classpath Loading from jar: C:\Program Files\apache-activemq-5.1.0\bin\win32\..\..\lib\activemq-core-5.1.0-tests.jar That depends on the camel -test jars as well. So you could add this .jar camel-core-1.4.0-tests.jar The -tests .jars is used as support classes for unit testing. So if you don't use unit testing then you could remove all the -tests .jars all together. Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: Jeff V [mailto:[EMAIL PROTECTED] Sent: 6. november 2008 21:43 To: [email protected] Subject: RE: Usage of Mina in camelContext for TCP loop. I appreciate your patience Claus. I changed that to use the full uri in my routes: <route> <from uri="mina:tcp://localhost:42000?textline=true&sync=false"/> <to uri="activemq:qA"/> </route> <route> <from uri="activemq:qA"/> <to uri="mina:tcp://localhost:42001?textline=true&sync=false"/> </route> This cause some exception explosions in my logs: http://www.nabble.com/file/p20369255/activemq.log activemq.log However, it seems I now have a tcp socket. That is accepting text lines. Sweet!!! -- View this message in context: http://www.nabble.com/Usage-of-Mina-in-camelContext-for-TCP-loop.-tp20348095s22882p20369255.html Sent from the Camel - Users mailing list archive at Nabble.com.
