There are likely more cases to consider where the classloader on the Thread could be different than expected.
Another place that comes to mind is the Direct VM component, where a boundary is crossed but I'm not sure what thread processes the message on the consumer side... I'll check and report back. Can anyone think of other potential areas where the classloader could be incoherent? Regards, Raúl Kripalani Apache Camel Committer Enterprise Architect, Program Manager, Open Source Integration specialist http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk
