Skip to Content
Last modified by Kieran Kelleher on 2012/07/19 21:12
From version 7.1
edited by Pascal Robert
on 2012/07/19 21:09
Change comment: added a warning
To version 8.1
edited by Pascal Robert
on 2012/07/19 21:12
Change comment: added a warning

Summary

Details

Page properties
Content
... ... @@ -8,7 +8,7 @@
8 8  
9 9  {{/code}}
10 10  
11 -The OGNL enable you to use the OGNL syntax for inline bindings (eg, putting bindings directly in the .html file instead of the .wod, for example: <wo:str value="$pageTitle" />). [[WOOGNL>>documentation:WOOgnl Framework]] is automatically added to the classpath when you create a new Wonder project.
11 +The OGNL enable you to use the OGNL syntax for inline bindings (eg, putting bindings directly in the .html file instead of the .wod, for example: <wo:str value="$pageTitle" />). [[WOOGNL>>WOOgnl Framework]] is automatically added to the classpath when you create a new Wonder project.
12 12  
13 13  {{code}}
14 14  
... ... @@ -66,7 +66,7 @@
66 66  
67 67  {{/code}}
68 68  
69 -Those properties, if used, allow you to specify the JDBC/EOF information for all of your models. See [[Best Practices-Properties Files>>WONDER:Best Practices-Properties Files]]
69 +Those properties, if used, allow you to specify the JDBC/EOF information for all of your models. See [[Best Practices-Properties Files>>Best Practices-Properties Files]]
70 70  
71 71  {{code}}
72 72  
... ... @@ -77,7 +77,7 @@
77 77  
78 78  {{/code}}
79 79  
80 -Those properties are to enable support for [[migrations>>WO:Project WONDER-Frameworks-ERXMigration]]. If you are using migrations but you have models where the schema already exist in the database, uncomment er.migration.modelNames and put in a list (comma separated) of the models you want to use migrations with, if you let this property commented, Wonder will try to migrate all of your models, which would generate errors for models where your schema already exist.
80 +Those properties are to enable support for [[migrations>>Project WONDER-Frameworks-ERXMigration]]. If you are using migrations but you have models where the schema already exist in the database, uncomment er.migration.modelNames and put in a list (comma separated) of the models you want to use migrations with, if you let this property commented, Wonder will try to migrate all of your models, which would generate errors for models where your schema already exist.
81 81  
82 82  {{code}}
83 83  
... ... @@ -119,7 +119,7 @@
119 119  
120 120  {{/code}}
121 121  
122 -Enable support for [[Click to Open]][[Click to Open>>WOL:Click to Open]] support in WOLips.
122 +Enable support for [[WONDER:Click to Open]][[Click to Open>>Click to Open]] support in WOLips.
123 123  
124 124  {{code}}
125 125  
... ... @@ -134,7 +134,7 @@
134 134  
135 135  {{/code}}
136 136  
137 -Check [[Project WONDER-Frameworks-ERJavaMail>>documentation:Project WONDER-Frameworks-ERJavaMail]] for an explanation.
137 +Check [[Project WONDER-Frameworks-ERJavaMail>>ERJavaMail Framework]] for an explanation.
138 138  
139 139  {{code}}
140 140