There was an issue related to cglib enhanced classes. That was fixed in
camel 2.2(http://issues.apache.org/activemq/browse/CAMEL-2384). Maybe the
problem could be similar?
capacman wrote:
>
> Hi all, in my project i have a bundle which exposes an interface as a osgi
> service and another bundle consume this service and use it in a
> camelcontext as a bean. Interface is:
>
> public interface ExampleService {
> // public methods go here...
>
> String scramble(@Header(value = "user") String user, @Body String
> body, Exchange exchange, @Property(value = "CamelTimerName") String
> timerName);
> }
>
> (just ignore @Header annotation and @Body annotation since they have to be
> null in this case). Given service implementation always see timerName
> parameter as null. Could not we use those annotations with osgi services?
>
>
>
--
View this message in context:
http://old.nabble.com/Camel-parameter-binding-annotations-with-osgi-services-tp28138255p28149814.html
Sent from the Camel - Users mailing list archive at Nabble.com.
