Version 2 by hannes on 09. November 2005, 12:30
| 3 | * Standard JS constructor, checks prototype to create instance of HopObject java class (we'll need to patch Rhino to do that, but this is actually a bug in Rhino IMO)IMO, i.e. JS objects should always use the same class as their prototypes anyway). |
| 4 | * Standard JS constructor, creates vanilla JS object, HopObject is vanilla JS object. Relational mapping is determined at script compile time, O/R layer uses standard Rhino API to inject/get inject/fetch relational data. |
Version 1 by hannes on 09. November 2005, 12:05
| 1 | Possible strategies for HopObject declarations in Helma 2: |
| 2 | |
| 3 | * Standard JS constructor, checks prototype to create instance of HopObject java class (we'll need to patch Rhino to do that, but this is actually a bug in Rhino IMO). |
| 4 | * Standard JS constructor, creates vanilla JS object, HopObject is vanilla JS object. Relational mapping is determined at script compile time, O/R layer uses standard Rhino API to inject/get relational data. |
| 5 | * Homegrown constructor installed at script compile time, creates instances of special Java HopObject class. |