Re: addTypeConverter does not clear misses in BaseTypeConverterRegistry

["Willem.Jiang" <wi...@gmail.com>]

Hi ,

Good catch of the issue of misses map. We should updated if a new
TypeConverter is added. Please feel free to create a JIRA for it, We love
the contribution :)


Can you give me more detail about the webstart issue of the 
AnnotationTypeConverterLoader?
What kind of error that you web start client faced, and why suppress the
usage of AnnotationTypeConverterLoader can make it work ?



Willem 

Andreas Kuhtz wrote:
> 
> Hello,
> 
> I was playing around with adding type converters after the context was
> started. In my tests I tried to convert an object without any type
> converter available (returns null which is fine). After that I added a
> matching type converter (manually) and run the conversion again. Because
> addTypeConverter does not clear misses map in BaseTypeConverterRegistry
> subsequent conversions fail.
> I think the misses map in BaseTypeConverterRegistry should remove the key
> if a matching type converter is added.
> 
> 
> My second problem is that it's currently not possible to start camel
> without the AnnotationTypeConverterLoader added. In case of a webstart
> based client application this causes startup errors that prevents using
> camel. 
> I added an attribute to suppress the usage of
> AnnotationTypeConverterLoader in my local sources and I've prepared a
> patch for this problem and the problem described above with test case.
> 
> Should I create a JIRA issue?
> 
>  http://camel.465427.n5.nabble.com/file/n4288871/patch-camel.diff
> patch-camel.diff 
> 
> Cheers 
> Andi
> 

--
View this message in context: http://camel.465427.n5.nabble.com/addTypeConverter-does-not-clear-misses-in-BaseTypeConverterRegistry-tp4288871p4290078.html
Sent from the Camel - Users mailing list archive at Nabble.com.