On Wed, Feb 16, 2011 at 9:33 AM, Chad Wilson <c.wil...@baml.com> wrote: > > Thanks Claus. > > Do you think this issue might affect BeanInfo use elsewhere in Camel, e.g. > in bean/simple expressions, or is the BeanInfo introspection repeated > separately for each exchange in those cases, thus not shared between > threads?
Its only a race condition on the very first invocation as it does remove getter/setters from the possible methods to choose from, if you haven't specified a fixed method name. Hence why it hasn't been seen before as its most likely hard to reproduce consistently between different OS, JVMs etc. And yes the same code would be used anyhow you let Camel invoke a method on a bean. > -- > View this message in context: > http://camel.465427.n5.nabble.com/Bean-component-BeanInfo-thread-safety-tp3387197p3387284.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
