2009/6/4 stevenmaring <steve.mar...@gmail.com>: > > yeah ... I fought with my local Archiva repo for quite some time yesterday > because it didn't seem to be proxying the SNAPSHOT requests onto the Apache > snapshot repo, so I manually inserted the 2.0-SNAPSHOT releases into my > Archiva repo. > > well ... with regard to this issue I'm having I'm not sure whether to put my > fist through the screen or curl up in the corner and cry like a baby ... > I've been fighting this for 3 days (on little sleep) and I'm supposed to > demo something with a code review in 7 hours!!!! I thought it would be cool > if I could show how I could make this company's life easier with Camel ... > it won't look good for Camel (in the eyes of my company) or ME (in this > economy as a contractor) if I can't get something working very soon. > > I've given up on trying to inject a handle to the ProducerTemplate into my > class since, given the CamelContext, I can easily create one > programmatically. So now, my only concern is how to get a handle to the > CamelContext into my POJO. > > I can see the context start in the logs, but it seems no matter what I try I > cannot get my CamelContext property set. It is always null. > > <camel:camelContext id="camel"/>
the camel: namespace is properly defined - and you've camel-spring on your classpath right? > <bean id="myBean" class="sample.MyBean"> > <property name="context" ref="camel"/> > </bean> That should work fine! BTW if your bean implements CamelContextAware it should get the CamelContext injected automatically - so long as the CamelContext is correctly. I wonder if its worth you submitting simple maven project with your POJO (remove all your company stuff) and we can get it working for you (then we can include it as an example)? -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
