Re: TypeConverterLoaderException in webstart

Thanks Andreas, this fix worked for me. Appreciate the help! Regards, Jim On 6/6/2011 12:12 AM, Andreas Kuhtz wrote: Found out that you must return at least one converter to make camel happy ... Use this updated method: public Set> findAnnotated(Class annotation,

RE: TypeConverterLoaderException in webstart

Found out that you must return at least one converter to make camel happy ... Use this updated method: public Set> findAnnotated(Class annotation, String... packageNames) { // we must return at least 1 converter Set> annotedCla

Re: TypeConverterLoaderException in webstart

FYI I opened a new JIRA issue at https://issues.apache.org/jira/browse/CAMEL-4026. On 5/26/2011 9:23 PM, Kuhtz, Andreas wrote: Hi, I had the same problem and the solution is easy. Just create a class that implements PackageScanClassResolver and define it as bean [1]. Camel will find it durin

Re: TypeConverterLoaderException in webstart

Hmm... the proposed resolution did not work for me after all. I'm not using xml configuration, so I didn't define the resolver as a bean, however it's my understanding that I can call context.setPackageScanClassResolver(). For example, my new test code: CamelContext context = new Def

Re: TypeConverterLoaderException in webstart

Hi Andreas, Thanks for the feedback. 1. So from what you are saying, it seems the classpath scanning is broken for webstart. I searched for jira issues and the only one I found is CAMEL-522 (reported by you; closed as "fixed" in Camel 1.5.0). Is this a regression of the same issue? Shoul

RE: TypeConverterLoaderException in webstart

Hi, I had the same problem and the solution is easy. Just create a class that implements PackageScanClassResolver and define it as bean [1]. Camel will find it during startup of the context and use this bean instead of creating the DefaultPackageScanClassResolver that scans the classpath. Maybe yo