L.S.,

A lot of ServiceMix 5 will be about being the best possible runtime
container for our beloved Camel routes, CXF services, ...  In my mind,
a lot of these extra goodies will happen automagically when you drop
routes/services/... in the container, so those bits would be 'under
the hood' and Scala will work out very good there imho.

When we allow people to plug into these container services, we
probably have to ensure to either make our Scala traits very
Java-friendly or allow them to register these extensions as Java
interfaces as well and we just translate them into the Scala thing
internally.  Anyway, we can definitely figure something out there that
allows people to write these extensions in any JVM language they like.


Regards,

Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



On Tue, Jul 12, 2011 at 6:15 PM, Johan Edstrom <seij...@gmail.com> wrote:
> A second comment would be :
>
> How do we deal with organizations that have started certifying Java and
> components?
> Pluggable infrastructure for multiple implementations?
>
> /je
>
> On Tue, Jul 12, 2011 at 10:04 AM, Johan Edstrom <seij...@gmail.com> wrote:
>
>> I have no problem whatsoever with Scala, I think that Apollo proved that.
>> And if we write an integrations platform where something like scala
>> provides
>> significant improvements, why not use it?
>>
>> I also think the ones savvy in scala will have to abide a lot of stupid
>> questions :)
>>
>> I do think that having a Java API is very important for existing customers
>> otherwise the change from JBI->OSGi->Scala will be a bit of a whirlwind.
>>
>> I think scala would do best if needed under the hood.
>>
>> But here are my +1 - Things will always be changing.
>>
>> Just look at how everything went to Apache Aries Blueprint.
>>
>> /je
>>
>>
>> On Jul 12, 2011, at 9:58 AM, Jean-Baptiste Onofré wrote:
>>
>> > Hi all,
>> >
>> > The low-hanging-fruit is a very good idea, and we added the same in
>> Karaf.
>> >
>> > Maybe, it's time to launch a formal vote about the Scala usage in
>> ServiceMix; wdyt ?
>> >
>> > Regards
>> > JB
>> >
>> >
>> >
>> > On Tue 12/07/11 17:26 , Ioannis Canellos  wrote::
>> >
>> >>
>> >> We'll still have plenty of Java code to go around in the other
>> >> subprojects but for ServiceMix 5, we now have a very good opportunity
>> >> to start with a new and clean codebase again and I think it definitely
>> >> makes sense to start with Scala there.
>> >
>> >
>> > I totally agree with Gert on this one.
>> >
>> >
>> >> As for making it easier for
>> >> people to start contributing, I think we should tag issues as 'low
>> >> hanging fruit' in JIRA if we think those are good for people to start
>> >> with and put that list on the website somewhere instead of holding
>> >> back on technology to achieve the same goal.
>> >>
>> >
>> > This is indeed a very interesting idea, which we might want to apply no
>> > matter what language we end up using.
>> >
>> > --
>> > *Ioannis Canellos*
>> > *
>> > http://iocanel.blogspot.com
>> >
>> > Apache Karaf http://karaf.apache.org/> Committer & PMC
>> > Apache ServiceMix http://servicemix.apache.org/>  Committer
>> > *
>> >
>> >
>> >
>> >
>>
>>
>

Reply via email to