> However the main problem I see is lack of organization in camel codebase. > Camel has gazilion of similar components which doesn't share anything except > core dependency.
Actually I must disagree as in my humble opinion organization of Camel code and it's internal reusability has nothing to do with writing Scala-related components in Scala. > There is lack of any abstractions for queueing components. > Introduction of scala may just make things worse since some functionality > will be never > ported to Java API. Unfortunately I must disagree again :) . If we come up with common components utility, we will create Scala wrapper over it and use this shared abstraction in Scala components as well. > Now, when I see a Scala on horizon I am afraid that components written in > Java will be slowly replaced by Scala. Nobody suggested to use Scala to write components referencing Java libraries. The subject of the discussion is focused only on components over Scala libraries. -- Henryk Konsek http://henryk-konsek.blogspot.com
