Skip to Content

Changes for page WebObjects and Squeryl

Last modified by Ravi Mendis on 2011/04/01 11:14
From version 94.1
edited by Ravi Mendis
on 2010/11/10 04:58
Change comment: There is no comment for this version
To version 95.1
edited by Ravi Mendis
on 2010/11/10 05:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,7 +14,7 @@
14 14  
15 15  = Migrating EOF -> Squeryl =
16 16  
17 -In contrast to EOF Squeryl maintains its ORM information programmatically - in the classes itself and collectively in a ##schema##. And in keeping with the strongly-typed philosophy of Scala, it has no dynamic component like EOF (i.e an EO model file).
17 +In contrast to EOF Squeryl maintains its ORM information programmatically - in the classes itself and collectively in a ##schema##. In keeping with the strongly-typed philosophy of Scala, Squeryl has no dynamic component like EOF (i.e an EO model file).
18 18  
19 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  
... ... @@ -22,7 +22,7 @@
22 22  
23 23  * 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 24  * Mark the abstract many-To-Many join entities as ##Abstract##.
25 -* (Temporary) Ensure all the model entities are in the same package. i.e ##model## <-> ##package## corresponds 1-to-1.
25 +* (Temporary) Ensure all the model entities are in the same package. i.e the package is exclusive to the model.
26 26  
27 27  === Generating the Squeryl Schema ===
28 28