Skip to Content
Last modified by Kieran Kelleher on 2012/07/19 21:12
From version 3.1
edited by Pascal Robert
on 2011/03/20 02:55
Change comment: There is no comment for this version
To version 4.1
edited by Pascal Robert
on 2011/03/20 02:52
Change comment: There is no comment for this version

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>>WO:Project WONDER-Frameworks-WOOgnl]] 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>>Project WONDER Frameworks WOOgnl]] is automatically added to the classpath when you create a new Wonder project.
12 12  
13 13  {{code}}
14 14  
... ... @@ -60,7 +60,7 @@
60 60  
61 61  {{/code}}
62 62  
63 -Those properties, if used, allow you to specify the JDBC/EOF information for all of your models. See [[WONDER:Best Practices-Properties Files]]
63 +Those properties, if used, allow you to specify the JDBC/EOF information for all of your models. See [[Best Practices Properties Files]]
64 64  
65 65  {{code}}
66 66  
... ... @@ -71,7 +71,7 @@
71 71  
72 72  {{/code}}
73 73  
74 -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.
74 +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.
75 75  
76 76  {{code}}
77 77  
... ... @@ -113,7 +113,7 @@
113 113  
114 114  {{/code}}
115 115  
116 -Enable support for [[|Click to Open]][[Click to Open>>WOL:Click to Open]] support in WOLips.
116 +Enable support for [[Click to Open]] support in WOLips.
117 117  
118 118  {{code}}
119 119  
... ... @@ -128,7 +128,7 @@
128 128  
129 129  {{/code}}
130 130  
131 -Check [[WO:Project WONDER-Frameworks-ERJavaMail]] for an explanation.
131 +Check [[Project WONDER-Frameworks-ERJavaMail]] for an explanation.
132 132  
133 133  {{code}}
134 134  
... ... @@ -160,7 +160,7 @@
160 160  
161 161  {{/code}}
162 162  
163 -With this set to DEBUG, all SQL stuff sent to your RDMS will show up in the console (or where you tell Log4J to send his stuff).
163 +With this set to DEBUG, all SQL stuff sent to your RDMS will show up in the console (or where you tell Log4J to send his stuff).
164 164  
165 165  {{code}}
166 166  
... ... @@ -170,3 +170,15 @@
170 170  {{/code}}
171 171  
172 172  See ERXSharedEOLoader.java in ERExtensions.
173 +
174 +{{code}}
175 +
176 +er.extensions.ERXNSLogLog4jBridge=INFO
177 +#log4j.logger.er.eo.ERXGenericRecord=DEBUG
178 +#log4j.logger.er.validation.ERXEntityClassDescription=DEBUG
179 +#log4j.logger.er.default.ERXEntityClassDescription=DEBUG
180 +log4j.logger.er.extensions.ERXDatabaseContextDelegate=WARN
181 +log4j.logger.er.extensions.ERXConfigurationManager=INFO
182 +#log4j.logger.er.extensions.ERXApplication.RequestHandling=DEBUG
183 +
184 +{{/code}}