Changes for page WebObjects and Squeryl
Last modified by Ravi Mendis on 2011/04/01 11:14
From version 155.1
edited by Ravi Mendis
on 2010/11/09 23:59
on 2010/11/09 23:59
Change comment:
There is no comment for this version
To version 150.1
edited by Ravi Mendis
on 2010/11/10 03:18
on 2010/11/10 03:18
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
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: Exploit ingthe 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,4 +16,24 @@ 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 though has the ability to generate classes in Java (and in Objective-C prior to WebObjects 4.5) 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 + 21 +=== Preparing your EO model === 22 + 23 +1. Make sure **all** EO entities have a class name (including abstract many-To-many "join" tables). There's no support for entities marked as ##EOGenericRecord##. 24 +1. (Temporary) Ensure all EO entities are in the same package 25 + 26 +=== Generating the Squeryl Schema === 27 + 28 +1. Create a .eogen file for your EO model as normal. Only set the ##File Names## extension to "scala". 29 +1. Use the Squeryl EO Templates: 30 + 31 +* 32 +** Entity.eotemplate [[template>>WOL:Squeryl _Entity.eotemplate]] 33 +** Entity.eotemplate [[template>>WOL:Squeryl Entity.eotemplate]] 34 + 35 +{{note title="Note"}} 36 + 37 +Any custom business "logic" will have to be manually re-written in Scala 38 + 39 +{{/note}}