Changes for page WebObjects and Squeryl

Last modified by Ravi Mendis on 2011/04/01 11:14

From version 130.1
edited by Ravi Mendis
on 2010/11/10 02:47
Change comment: There is no comment for this version
To version 131.1
edited by Ravi Mendis
on 2010/11/10 03:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,10 +6,10 @@
6 6  ** Spawns multiple database connections
7 7  ** Issues database transactions concurrently
8 8  * Scala Actor compatible
9 -* Immutable object model/graph
9 +** Immutable object model/graph
10 10  * Strongly-typed
11 -** Better suited for business "logic".
12 - E.g: Exploiting the compiler and IDE to catch exceptions at compile time rather than at run-time.
11 +** Better suited for database/business "logic".
12 + E.g: Exploits the compiler and IDE to catch exceptions at compile time rather than at run-time.
13 13  * Uses Scala (functional) collection classes
14 14  
15 15  = Migrating EOF -> Squeryl =
... ... @@ -16,8 +16,10 @@
16 16  
17 17  In keeping with the strong-typed philosophy of Scala, Squeryl has no dynamic component like EOF (i.e an EO model file).
18 18  
19 -EOF has the ability to generate classes in Java (and in Objective-C prior to WebObjects 4.5). So enforcing type as has become customary in enterprise environments. We may exploit this feature of EOF to generate a Squeryl schema.
19 +EOF has the ability to generate classes in Java (and in Objective-C prior to WebObjects 4.5) as enforcing type has become customary in enterprise environments. We may exploit this feature of EOF to generate a Squeryl schema.
20 20  
21 +== Generating Squeryl Schema ==
22 +
21 21  1. Create a .eogen file for your EO model as normal. Only set the ##File Names## extension to "scala".
22 22  1. Use the Squeryl EO Templates:
23 23  
... ... @@ -24,3 +24,9 @@
24 24  *
25 25  ** Entity.eotemplate [[template>>WOL:Squeryl _Entity.eotemplate]]
26 26  ** Entity.eotemplate [[template>>WOL:Squeryl Entity.eotemplate]]
29 +
30 +{{note title="Note"}}
31 +
32 +Any custom business "logic" will have to be manually re-written in Scala
33 +
34 +{{/note}}