Wiki source code of WebObjects with Scala
Version 481.1 by Ravi Mendis on 2010/12/23 23:58
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | === What is Scala? === | ||
| 2 | |||
| 3 | [[Scala>>http://en.wikipedia.org/wiki/Scala_(programming_language)]] is a JVM language that is a hybrid of Object-Oriented and Functional styles. Its [[functional language>>http://en.wikipedia.org/wiki/Functional_programming]] foundations and built-in Actors library makes it especially attractive for concurrent computing. In this day and age of multi-core processors concurrent computing can not be ignored. | ||
| 4 | |||
| 5 | Many of Scala's features have been designed with concurrency in mind, some of which may not be unfamiliar to Objective-C or WebObjects developers. Here's a summary: | ||
| 6 | |||
| 7 | |= |= Objective-C |= Java |= Scala | ||
| 8 | |= Immutability | Collections //e.g: NSArray/NSMutableArray// | No | Yes | ||
| 9 | |= Closures | Blocks (//Extension//) | No | Anonymous Functions | ||
| 10 | |= Static variables | Yes | Yes | No | ||
| 11 | |= Static methods or functions | Yes | Yes | No | ||
| 12 | |= Concurrency | [[Grand Central Dispatch>>http://en.wikipedia.org/wiki/Grand_Central_Dispatch]] (//Extension//) | //Threads// | [[Actors>>http://en.wikipedia.org/wiki/Actor_model]] | ||
| 13 | |= |= Weakly Typed |= --Strongly Typed-- |= Strongly Typed | ||
| 14 | |||
| 15 | Other notable features include: | ||
| 16 | |||
| 17 | |= |= Objective-C |= Java |= Scala | ||
| 18 | |= Parametered methods | Yes //e.g: addObject: to~:// | No | Yes //e.g: add(object= ,to=)// | ||
| 19 | |= Class composition | Categories | Interfaces | Traits | ||
| 20 | |||
| 21 | === Why Use Scala? === | ||
| 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. | ||
| 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 | === Can WebObjects be Programmed In Scala? === | ||
| 29 | |||
| 30 | Yes. It is very simple. | ||
| 31 | Scala compiles to java bytecode. | ||
| 32 | |||
| 33 | Furthermore, being a multi-paradigm language grants Scala easy WebObjects-interoperability. | ||
| 34 | |||
| 35 | ===== Caveats ===== | ||
| 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. | ||
| 38 | |||
| 39 | = WebObjects In Scala = | ||
| 40 | |||
| 41 | The following highlights some of the differences between Java and Scala in WebObjects: | ||
| 42 | |||
| 43 | == EOs in Scala == | ||
| 44 | |||
| 45 | === Thread-Safe Shared Vars === | ||
| 46 | |||
| 47 | Scala doesn't have static variables or methods. Instead Scala employs the [[Singleton Pattern>>http://en.wikipedia.org/wiki/Singleton_pattern]] which is built into the language and is **thread-safe**: a class can have a //Companion Object// that will allow you to achieve something equivalent to static variables - but better. | ||
| 48 | |||
| 49 | You don't have to worry about synchronizing access to shared mutable fields in a concurrent application. | ||
| 50 | This is not however true for mutable ##val## e.g: ##NSMutableArray##, ##scala.collection.mutable.ListBuffer## which you will have to synchronize the adding to or removing from. | ||
| 51 | |||
| 52 | The following is an example of the use of a //Companion Object// for Talent in Scala instead of Talent static fields in Java. | ||
| 53 | |||
| 54 | Java: | ||
| 55 | |||
| 56 | {{code value="java"}} | ||
| 57 | |||
| 58 | public class _Talent extends EOGenericRecord { | ||
| 59 | public static final String ENTITY_NAME = "Talent"; | ||
| 60 | |||
| 61 | {{/code}} | ||
| 62 | |||
| 63 | Scala: | ||
| 64 | |||
| 65 | {{code}} | ||
| 66 | |||
| 67 | object Talent extends EOGenericRecord { | ||
| 68 | val ENTITY_NAME = "Talent" | ||
| 69 | |||
| 70 | {{/code}} | ||
| 71 | |||
| 72 | This value will be accessed exactly the same way in both languages: | ||
| 73 | |||
| 74 | {{code}} | ||
| 75 | |||
| 76 | Talent.ENTITY_NAME | ||
| 77 | |||
| 78 | {{/code}} | ||
| 79 | |||
| 80 | ==== Compacted imports ==== | ||
| 81 | |||
| 82 | Two lines in Java are compacted into one in Scala. | ||
| 83 | |||
| 84 | In Java: | ||
| 85 | |||
| 86 | {{code value="java"}} | ||
| 87 | |||
| 88 | import com.webobjects.eocontrol.EOGenericRecord; | ||
| 89 | import com.webobjects.eocontrol.EORelationshipManipulation; | ||
| 90 | |||
| 91 | {{/code}} | ||
| 92 | |||
| 93 | In Scala: | ||
| 94 | |||
| 95 | {{code}} | ||
| 96 | |||
| 97 | import com.webobjects.eocontrol.{EOGenericRecord, EORelationshipManipulation} | ||
| 98 | |||
| 99 | {{/code}} | ||
| 100 | |||
| 101 | == WOComponents in Scala == | ||
| 102 | |||
| 103 | ==== Compact Constructors ==== | ||
| 104 | |||
| 105 | Scala allows for simpler use of multi-valued constructors than Java. | ||
| 106 | |||
| 107 | In Java: | ||
| 108 | |||
| 109 | {{code value="java"}} | ||
| 110 | |||
| 111 | public class MenuHeader extends WOComponent { | ||
| 112 | |||
| 113 | public MenuHeader(WOContext aContext) { | ||
| 114 | super(aContext); | ||
| 115 | } | ||
| 116 | |||
| 117 | {{/code}} | ||
| 118 | |||
| 119 | In Scala: | ||
| 120 | |||
| 121 | {{code}} | ||
| 122 | |||
| 123 | class MenuHeader(context: WOContext) extends WOComponent(context: WOContext) { | ||
| 124 | |||
| 125 | {{/code}} | ||
| 126 | |||
| 127 | ==== Simplified Exception Handling ==== | ||
| 128 | |||
| 129 | Scala doesn't force you to catch exceptions unlike in Java. | ||
| 130 | In addition, the syntax employs Scala's very powerful **pattern matching** to handle exceptions. | ||
| 131 | |||
| 132 | In Java: | ||
| 133 | |||
| 134 | {{code value="java"}} | ||
| 135 | |||
| 136 | try { | ||
| 137 | EditPageInterface epi = D2W.factory().editPageForNewObjectWithEntityNamed(_manipulatedEntityName, session()); | ||
| 138 | epi.setNextPage(context().page()); | ||
| 139 | nextPage = (WOComponent) epi; | ||
| 140 | } catch (IllegalArgumentException e) { | ||
| 141 | ErrorPageInterface epf = D2W.factory().errorPage(session()); | ||
| 142 | epf.setMessage(e.toString()); | ||
| 143 | epf.setNextPage(context().page()); | ||
| 144 | nextPage = (WOComponent) epf; | ||
| 145 | } | ||
| 146 | |||
| 147 | {{/code}} | ||
| 148 | |||
| 149 | In Scala: | ||
| 150 | |||
| 151 | {{code}} | ||
| 152 | |||
| 153 | try { | ||
| 154 | var epi: EditPageInterface = D2W.factory.editPageForNewObjectWithEntityNamed(_manipulatedEntityName, session) | ||
| 155 | epi.setNextPage(context.page) | ||
| 156 | nextPage = epi.asInstanceOf[WOComponent] | ||
| 157 | } catch { | ||
| 158 | case e: IllegalArgumentException => { | ||
| 159 | var epf: ErrorPageInterface = D2W.factory.errorPage(session) | ||
| 160 | epf.setMessage(e.toString) | ||
| 161 | epf.setNextPage(context.page) | ||
| 162 | nextPage = epf.asInstanceOf[WOComponent] | ||
| 163 | } | ||
| 164 | } | ||
| 165 | |||
| 166 | {{/code}} | ||
| 167 | |||
| 168 | ==== Scala Annotations vs. Generated Accessors ==== | ||
| 169 | |||
| 170 | An example of accessing variables in WebObjects with the following languages: | ||
| 171 | |||
| 172 | |= |= Objective-C |= Java |= Scala | ||
| 173 | |= getter | ##object name## | ##object.name()## | ##object.name## | ||
| 174 | |= setter | ##object setName:aName## | ##object.setName(aName)## | ##object.name = aName## | ||
| 175 | |||
| 176 | Of course in Java, we may generate WebObjects classes with "get" methods as well in order to stick to convention. | ||
| 177 | In scala there is an additional convenience we may use to produce "get" and "set" methods in addition to the default Scala accessors - Scala Annotations. | ||
| 178 | |||
| 179 | E.g, in Main.scala we annotate our component keys with ##@BeanProperty## to automatically create public "set" and "get" methods. | ||
| 180 | These variables can then be accessed via //KVC//. | ||
| 181 | |||
| 182 | {{code}} | ||
| 183 | |||
| 184 | import scala.reflect.BeanProperty | ||
| 185 | |||
| 186 | @BeanProperty var username = new String() | ||
| 187 | @BeanProperty var password = new String() | ||
| 188 | @BeanProperty var isAssistantCheckboxVisible = false | ||
| 189 | |||
| 190 | {{/code}} | ||
| 191 | |||
| 192 | == How to Use Scala Collections with EOF == | ||
| 193 | |||
| 194 | To use the Scala Collections API with an NSArray or NSDictionary you simply need to add an import: | ||
| 195 | |||
| 196 | {{code value="java"}} | ||
| 197 | |||
| 198 | import scala.collection.JavaConversions._ | ||
| 199 | |||
| 200 | {{/code}} | ||
| 201 | |||
| 202 | After that, you may access the typical Scala collection methods directly on NSArray. This employs a feature of Scala known as implicit conversions to automagically cast a NSArray (a Java Iterable) into a Scala Iterable while leaving the actual object unchanged. Alternatively, you could generate an actual new scala.List instance by calling myNSArray.toList. | ||
| 203 | |||
| 204 | == How to Add Scala to a WO Project == | ||
| 205 | |||
| 206 | {{include value="WOL:Adding Scala Support to a WOLips Project"}}{{/include}} | ||
| 207 | |||
| 208 | {{note}} | ||
| 209 | |||
| 210 | This is for Eclipse/WOLips IDE | ||
| 211 | |||
| 212 | {{/note}} | ||
| 213 | |||
| 214 | == WO Scala Example == | ||
| 215 | |||
| 216 | The following example is an almost 100% Scala WO app. In reality it is a mixed Java/Scala app: | ||
| 217 | All the EO logic and WO components are in Scala. | ||
| 218 | Only the Application class remains Java. | ||
| 219 | |||
| 220 | It is based on the D2W Movies example. | ||
| 221 | |||
| 222 | {{attachments patterns=".*zip"}}{{/attachments}} | ||
| 223 | |||
| 224 | === Setup === | ||
| 225 | |||
| 226 | 1. [[Install the Scala eclipse IDE>>http://www.scala-ide.org/]] | ||
| 227 | 1. Right-click on Application.java and run as a WOApplication (as usual). | ||
| 228 | |||
| 229 | Application can be made into a Scala class as well, but then you will have to create a launcher in Eclipse manually. | ||
| 230 | |||
| 231 | == EO Templates == | ||
| 232 | |||
| 233 | When you create your ##.eogen## file, be sure to make the following changes in the EOGenerator Editor: | ||
| 234 | |||
| 235 | 1. Point to the local [[Scala versions>>http://wiki.objectstyle.org/confluence/display/WOL/EOGenerator+Templates+and+Additions]] of the .eotemplate files for ##Entity## and ##Entity## | ||
| 236 | 1. Change the File Names Extension to "scala" | ||
| 237 | 1. In Destination Paths set the Superclass Package (e.g: base) | ||
| 238 | 1. Uncheck Java under Options | ||
| 239 | |||
| 240 | == How to Build & Deploy a WebObjects Scala Project with Ant == | ||
| 241 | |||
| 242 | 1. [[Download>>http://www.scala-lang.org/downloads]] and install Scala | ||
| 243 | 1. Set ##scala.home## (the location Scala has been installed onto) in the project ##build.properties## file | ||
| 244 | 1. [[Add the scalac task and properties>>Configuring Ant to Build Scala with WebObjects]] to the ant build.xml file | ||
| 245 | 1. Run from the project directory: ##sudo ant clean install## |