Skip to Content

Changes for page WebObjects with Scala

Last modified by Ravi Mendis on 2011/05/10 02:10
From version 486.1
edited by Ravi Mendis
on 2010/12/24 00:07
Change comment: There is no comment for this version
To version 487.1
edited by Ravi Mendis
on 2010/12/24 00:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -20,11 +20,8 @@
20 20  
21 21  === Why Use Scala? ===
22 22  
23 -Scala can help you to write thread-safe code.
24 -It has concurrency that is built-in to the standard library, primarily via Actors.
23 +For WebObjects developers, Scala offers itself as a powerful, safe and easy-to-use solution for [[concurrent computing>>Building Concurrent Applications with WebObjects and Scala]]. (In other words, Scala Actors can be used for problems that would have normally required threads).
25 25  
26 -So for WebObjects developers, Scala offers itself as a powerful, safe and easy-to-use solution for [[concurrent applications>>Building Concurrent Applications with WebObjects and Scala]]. (In other words, Scala Actors can be used for problems that would have normally required threads).
27 -
28 28  === Can WebObjects be Programmed In Scala? ===
29 29  
30 30  Yes. It is very simple.
... ... @@ -34,7 +34,7 @@
34 34  
35 35  ===== Caveats =====
36 36  
37 -Tool support is a weak point. If your Application class is in Scala then you will have to create an Eclipse launch configuration manually. Also the [[Scala plugin>>http://www.scala-ide.org]] is rather slow and still very buggy.
34 +Legacy tool support is often cited as a weak point. If your Application class is in Scala then you will have to create an Eclipse launch configuration manually. Also the [[Scala plugin>>http://www.scala-ide.org]] can be slow at times and sometimes buggy.
38 38  
39 39  = WebObjects In Scala =
40 40