Skip to Content

Wiki source code of WebObjects with Scala

Version 517.1 by Ravi Mendis on 2010/04/06 18:25
Show last authors
1 === What is Scala? ===
2
3 [[Scala>>http://en.wikipedia.org/wiki/Scala_(programming_language)]] is a language for concurrent computing.
4 In this day and age of multi-core processors, concurrent computing can't be ignored.
5
6 Many of Scala's features have been designed with concurrency in mind.
7 Some of these may not be unfamiliar to Objective-C or WebObjects developers.
8
9 Here's a quick summary:
10
11 |= |= Objective-C |= Java |= Scala
12 |= Separation of Mutable & Immuable Datatypes | Collections //e.g: NSArray/NSMutableArray// | No | Yes
13 |= Closures | Blocks (//Extension//) | No | Anonymous Functions
14 |= Static variables | Yes | Yes | No
15 |= Static methods or functions | Yes | Yes | No
16 |= Concurrency | [[Grand Central Dispatch>>http://en.wikipedia.org/wiki/Grand_Central_Dispatch]] (//Extension//)| //Threads// |[[Actors>>http://en.wikipedia.org/wiki/Actor_model]]
17 |= |= Weakly Typed |=--Strongly Typed--|= Strongly Typed
18
19 Other notable features include:
20
21 |= |= Objective-C |= Java |= Scala
22 |= Parametered methods | Yes //e.g: addObject: to~:// | No | Yes //e.g: add(object= ,to=)//
23 |= Class composition | Categories | Interfaces | Traits
24
25 === Why Use Scala? ===
26
27 Scala is inherently thread-safe.
28 It has concurrency that is effectively built-in to the language.
29
30 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).
31
32 === Can WebObjects be Programmed In Scala? ===
33
34 Yes. It is very simple.
35 Scala compiles to java bytecode. Hence using it with WebObjects is fairly straightforward.
36
37 = WebObjects In Scala =
38
39 The following highlights some of the differences between Java and Scala in WebObjects:
40
41 == EOs in Scala ==
42
43 === Thread-Safe Shared Vars ===
44
45 Scala doesn't have static variables or methods. However, a class can have a //Companion Object// that will allow you to achieve something equivalent to static variables.
46 One of the advantages of this approach is that it is **thread-safe**, so you don't have to worry about synchronizing access to these fields in a concurrent application.
47
48 The following is an example of the use of a //Companion Object// for Talent in Scala instead of Talent static fields in Java.
49
50 Java:
51
52 {{code value="java"}}
53
54 public class _Talent extends EOGenericRecord {
55 public static final String ENTITY_NAME = "Talent";
56
57 {{/code}}
58
59 Scala:
60
61 {{code}}
62
63 object Talent extends EOGenericRecord {
64 val ENTITY_NAME = "Talent"
65
66 {{/code}}
67
68 This value will be accessed exactly the same way in both languages:
69
70 {{code}}
71
72 Talent.ENTITY_NAME
73
74 {{/code}}
75
76 ==== Compacted imports ====
77
78 Two lines in Java are compacted into one in Scala.
79
80 In Java:
81
82 {{code value="java"}}
83
84 import com.webobjects.eocontrol.EOGenericRecord;
85 import com.webobjects.eocontrol.EORelationshipManipulation;
86
87 {{/code}}
88
89 In Scala:
90
91 {{code}}
92
93 import com.webobjects.eocontrol.{EOGenericRecord, EORelationshipManipulation}
94
95 {{/code}}
96
97 == WOComponents in Scala ==
98
99 ==== Compact Constructors ====
100
101 Scala allows for simpler use of multi-valued constructors than Java.
102
103 In Java:
104
105 {{code value="java"}}
106
107 public class MenuHeader extends WOComponent {
108
109 public MenuHeader(WOContext aContext) {
110 super(aContext);
111 }
112
113 {{/code}}
114
115 In Scala:
116
117 {{code}}
118
119 class MenuHeader(context: WOContext) extends WOComponent(context: WOContext) {
120
121 {{/code}}
122
123 ==== Simplified Exception Handling ====
124
125 Scala doesn't force you to catch exceptions unlike in Java.
126 In addition, the syntax employs Scala's very powerful **pattern matching** to handle exceptions.
127
128 In Java:
129
130 {{code value="java"}}
131
132 try {
133 EditPageInterface epi = D2W.factory().editPageForNewObjectWithEntityNamed(_manipulatedEntityName, session());
134 epi.setNextPage(context().page());
135 nextPage = (WOComponent) epi;
136 } catch (IllegalArgumentException e) {
137 ErrorPageInterface epf = D2W.factory().errorPage(session());
138 epf.setMessage(e.toString());
139 epf.setNextPage(context().page());
140 nextPage = (WOComponent) epf;
141 }
142
143 {{/code}}
144
145 In Scala:
146
147 {{code}}
148
149 try {
150 var epi: EditPageInterface = D2W.factory.editPageForNewObjectWithEntityNamed(_manipulatedEntityName, session)
151 epi.setNextPage(context.page)
152 nextPage = epi.asInstanceOf[WOComponent]
153 } catch {
154 case e: IllegalArgumentException => {
155 var epf: ErrorPageInterface = D2W.factory.errorPage(session)
156 epf.setMessage(e.toString)
157 epf.setNextPage(context.page)
158 nextPage = epf.asInstanceOf[WOComponent]
159 }
160 }
161
162 {{/code}}
163
164 ==== Scala Annotations vs. Generated Accessors ====
165
166 An example of accessing variables in WebObjects with the following languages:
167
168 |= |= Objective-C |= Java |= Scala
169 |= getter | ##object name## | ##object.name()## | ##object.name##
170 |= setter | ##object setName:aName## | ##object.setName(aName)## | ##object.name = aName##
171
172 Of course in Java, we may generate WebObjects classes with "get" methods as well in order to stick to convention.
173 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.
174
175 E.g, in Main.scala we annotate our component keys with ##@BeanProperty## to automatically create public "set" and "get" methods.
176 These variables can then be accessed via //KVC//.
177
178 {{code}}
179
180 import scala.reflect.BeanProperty
181
182 @BeanProperty var username = new String()
183 @BeanProperty var password = new String()
184 @BeanProperty var isAssistantCheckboxVisible = false
185
186 {{/code}}
187
188 == How to Use Scala Collections with EOF ==
189
190 One of the benefits of Scala is its very powerful, concurrency-ready collection classes - primarily ##List##, ##Map## and ##Set##.
191 Employing these instead of ##NSArray## and ##NSDictionary## in WebObjects/EOF may be challenging.
192
193 But one may modify the EO templates to produce API such as:
194
195 {{code}}
196
197 def movies: NSArray[Studio] = {
198 storedValueForKey(_Studio.Keys.MOVIES).asInstanceOf[NSArray[Studio]]
199 }
200
201 def moviesList: List[Studio] = {
202 movies.objects.toList
203 }
204
205 {{/code}}
206
207 == How to Add Scala to a WO Project ==
208
209 {{include value="WOL:Adding Scala Support to a WOLips Project"}}{{/include}}
210
211 {{note}}
212
213 This is for Eclipse/WOLips IDE
214
215 {{/note}}
216
217 == WO Scala Example ==
218
219 The following example is an almost 100% Scala WO app. In reality it is a mixed Java/Scala app:
220 All the EO logic and WO components are in Scala.
221 Only the Application class is Java.
222
223 It is based on the D2W Movies example.
224
225 {{attachments patterns=".*zip"}}{{/attachments}}
226
227 === Setup ===
228
229 1. [[Install the Scala eclipse IDE>>http://www.scala-lang.org/node/94]]
230 1. Install and start the OpenBase OBMovies database.
231 1. Right-click on Application.java and run as a WOApplication (as usual).
232
233 ==== EO Templates ====
234
235 When you create your ##.eogen## file, be sure to make the following changes in the EOGenerator Editor:
236
237 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//##
238 1. Change the File Names Extension to "scala"
239 1. In Destination Paths set the Superclass Package (e.g: base)
240 1. Uncheck Java under Options
241
242 == How to Build & Deploy a WebObjects Scala Project with Ant ==
243
244 1. [[Download>>http://www.scala-lang.org/downloads]] and install Scala
245 1. Set ##scala.home## (the location Scala has been installed onto) in the project ##build.properties## file
246 1. [[Add the scalac task and properties>>Configuring Ant to Build Scala with WebObjects]] to the ant build.xml file
247 1. Run from the project directory: ##sudo ant clean install##
248
249 == Caveats ==
250
251 {{warning}}
252
253 Currently mixed Scala and Java projects aren't supported by the Scala Eclipse IDE, though it is possible to do so providing your project is either mostly Java or mostly Scala.
254
255 {{/warning}}