I know there are some people who are able to support scala in Camel repositories. 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. 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. If you could take a look on JMS/SJMS components you will see same constants put in different utility classes. Both components do same things, support same syntax of destination selecting (another portion of duplicated code) and must use connection factory.
Now, when I see a Scala on horizon I am afraid that components written in Java will be slowly replaced by Scala. There is already an old camel-stomp component on github [1], but it was written without scala wrapper library. Quo vadis Camel? [1] https://github.com/pedroteixeira/camel-stomp Cheers, :-) Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana przez Henryk Konsek <hekon...@gmail.com> w dniu 18 lut 2013, o godz. 11:18: > Some extra thoughts from my side. > > -1 for writing Scala-related components in Java > Using Java to write components referencing Scala libraries is a bad > idea in my humble opinion. Such code is hard to maintain and will not > encourage Scala people to contribute. I also believe that if somebody > doesn't know Scala, then he won't help us to maintain for example Akka > anyway, even if the component itself is written in Java. > > It would be nice if our community could communicate that we are open > for Scala contributors here at Camel. I don't want us to create the > vicious circle rejecting possible Scala committers from our community. > > I also think that creating another community will generate unnecessary > release and maintenance burden. Take a look at Camel Extra and all the > additional effort it requires. I understand that we need to keep Camel > Extra separated due to the licensing reasons, so this burden is > unavoidable. However this is avoidable in the case of Scala. > > Willem: >> Scala is hot, I'm willing to help the Scala related components in Apache >> camel repository. > > That makes two of us. Anybody else interested in showing Scala some > extra love ? :) > > Willem: >> As Scala has some back compatible issue, I think we can consider to create a >> sub project in camel which can host the Scala related components > > The first (successful) attempt to settle strategy for handling binary > compatibility has been done in camel-scala module. But I would defer > this topic to another discussion, as Scala binary compatibility is a > larger subject itself :) . > > Anybody any further thoughts? > > -- > Henryk Konsek > http://henryk-konsek.blogspot.com
