Hi
You most likely need Camel 2.2 to use Spring 3.0 as Spring 3.0 change
something in their JMS implementation.
http://camel.apache.org/camel-220-release.html
http://camel.apache.org/download.html
On Sat, Jan 16, 2010 at 11:49 PM, rbolkey wrote:
>
> Hi all,
>
> Context: Camel 2.1.0 and Spring JM
I know it, this is a my miss-understanding of camel's Processor;
My work is not provide application for ending-user, but for
another-develop-team to use. So the code of the processor cannot be
full-controlled by my-self.
Anyway using Camel, I could extend to support the feature easily. This is
ca
It doesn't appear that the file uploaded correctly, here it is in zip format.
http://old.nabble.com/file/p27195503/camel-jboss.zip camel-jboss.zip
pmmerritt wrote:
>
> I finally figured out what was going on and it turned out just to be an
> issue with the LOG not getting initialized properly
I finally figured out what was going on and it turned out just to be an issue
with the LOG not getting initialized properly which was throwing a low level
null pointer that was not being logged anywhere. I took the liberty to
create the attached project named camel-jboss which contains the working
Hi all,
Context: Camel 2.1.0 and Spring JMS 3.0.0.RELEASE
I'm having a problem, and I think the issue is that Camel's JMS Requestor
doesn't start the Spring SimpleMessageListenerContainer that it creates?
Requestor#doStart() calls the container's afterPropertiesSet, but doesn't
call the contain
Hi,
I'm using Camel 1.6 with ServiceMix 3.3.
This is my route :
JBI JMS consumer (with ServiceMix) -> Camel JBI endpoint -> Bean.
My JMS consumer is XA transacted and when it fails to call the Camel JBI
endpoint, the JMS Message is rolledback into the queue (this is what I
want).
But if I call
On Sat, Jan 16, 2010 at 8:26 AM, ext2 wrote:
> This is a bad news for me.
>
> Processor is very useful for customized message transformer, but now it
> seems the processor cannot provide MEP-independent feature. I must deal with
> all the MEP of camel correctly in the Processor if I want to re-use
I understand problem.
Jabber protocol used direct socket connection. To available connection
througth "proxy", must be define java properties "socksproxySet",
"socksProxyPort", "socksProxyHost". For example, direct in source
//System.setProperty("socksproxySet","true");
//System
On Fri, Jan 15, 2010 at 5:56 PM, pmmerritt wrote:
>
> I implemented the VFSPackageScanClassResolver as discussed
> http://codeandtell.wordpress.com/2009/03/03/apache-camel-jboss-5-spring/
> Apache Camel JBoss 5
> and plugged it in to the camel route and it is recognized by camel as is
> evident by
