Hi On 26/08/13 16:11, glsilverman wrote:
Thanks for your reply. I'm using Camel 2.11.1 and CXF version 2.7.5. The key dependency, as I nderstand it, is on cxf-rt-rs-extension-search, which is available. I'm running Karaf 2.3.2. I'm sure it's a configuration issue in blueprint and whether I have to do more than simply register SearchContextProvider as a cxf provider in order be able to inject a SerachContext object.
I'm only aware of the following issue resolved awhile back: https://issues.apache.org/jira/browse/CXF-4508,
I've also seen users reporting Null contexts returned by the runtime when an actual FIQL expression contains the properties which can not be mapped to a bean; returning null in such cases seemed reasonable to me at a time because typically the users won't get an HTTP error back when mistyping some query - so please double check the expression can be mapped. Consider a workaround: add SearchContext as method parameter, if it is still null then it is most likely not Camel CXFRS or Blueprint related issue
Other than that I've no idea what may be causing the issue - please consider creating a simple Camel-based test project and I will investigate further;
thanks, Sergey
-- View this message in context: http://camel.465427.n5.nabble.com/How-can-I-configure-and-use-SearchContext-in-CXFRS-tp5737843p5737980.html Sent from the Camel - Users mailing list archive at Nabble.com.
