Skip to Content
Version 2.1 by Pascal Robert on 2011/03/20 02:55
Show last authors
1 When you create a new Wonder project in WOLips, the Properties file is filled with numerous properties. If you are new to WebObjects or new to using Project Wonder, you might want to know what those properties do. Let's see:
2
3 {{code}}
4
5 # OGNL
6 ognl.helperFunctions=true
7 ognl.inlineBindings=true
8
9 {{/code}}
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.
12
13 {{code}}
14
15 # Misc
16 er.extensions.stackTrace.cleanup=true
17
18 {{/code}}
19
20 See ERXExceptionUtilities.printStackTrace
21
22 {{code}}
23
24 # EOF
25 er.extensions.ERXEC.safeLocking=true
26
27 {{/code}}
28
29 This one is to enable editing context auto-locking (eg, you don't have to lock/unlock it yourself) at the end of the RR loop. You have to create your editing context with ERXEC.newEditingContext.
30
31 {{code}}
32
33 er.extensions.ERXEC.useSharedEditingContext=false
34
35 {{/code}}
36
37 If set to true, newly created instances use the shared editing context.
38
39 {{code}}
40
41 er.extensions.ERXEnterpriseObject.applyRestrictingQualifierOnInsert=true
42
43 {{/code}}
44
45 From what I understand, the "Qualifier" field defined in the model for an entity will not be used if you set this property to false.
46
47 {{code}}
48
49 er.extensions.ERXEnterpriseObject.updateInverseRelationships=true
50
51 {{/code}}
52
53 Provides automatic inverse relationship updating for ERXGenericRecord and ERXCustomObject.
54
55 {{code}}
56
57 #dbConnectURLGLOBAL=
58 #dbConnectUserGLOBAL=
59 #dbConnectPasswordGLOBAL=
60
61 {{/code}}
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]]
64
65 {{code}}
66
67 # Migrations
68 #er.migration.migrateAtStartup=true
69 #er.migration.createTablesIfNecessary=true
70 #er.migration.modelNames=YourModel
71
72 {{/code}}
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.
75
76 {{code}}
77
78 # Misc Components
79 #er.extensions.ERXWOForm.multipleSubmitDefault=true
80
81 {{/code}}
82
83 Set the "multipleSubmit" binding of WOForm to true for all WOForm instances. Uncomment that property if you don't want to remember to set that dreaded binding on every form.
84
85 {{code}}
86
87 #er.extensions.ERXWORepetition.checkHashCodes=true
88
89 {{/code}}
90
91 Help with backtracking issues by adding not only the current index, but also the current object's hash code to the element id (see ERXWORepetition API).
92
93 {{code}}
94
95 #er.extensions.ERXWORepetition.raiseOnUnmatchedObject=true
96
97 {{/code}}
98
99 If this property is set to true, an ERXWORepetition.UnmatchedObjectException} is thrown if notFoundMarker is bound, that is used for the item in the repetition. (see ERXWORepetition API).
100
101 {{code}}
102
103 #er.extensions.ERXWORepetition.eoSupport=true
104
105 {{/code}}
106
107 Try to use globalIDs to determine the hashCode for EOs.
108
109 {{code}}
110
111 #er.component.clickToOpen=true
112 #wolips.password=wo
113
114 {{/code}}
115
116 Enable support for [[|Click to Open]][[Click to Open>>WOL:Click to Open]] support in WOLips.
117
118 {{code}}
119
120 # ERJavaMail
121 er.javamail.centralize=true
122 er.javamail.adminEmail=admin@yourhost.com
123 er.javamail.debugEnabled=false
124 er.javamail.smtpHost=your.smtpserver.com
125 er.javamail.smtpAuth=false
126 er.javamail.smtpUser=
127 er.javamail.smtpPassword=
128
129 {{/code}}
130
131 Check [[WO:Project WONDER-Frameworks-ERJavaMail]] for an explanation.
132
133 {{code}}
134
135 # Log4j Configuration
136 log4j.loggerFactory=er.extensions.logging.ERXLogger$Factory
137 log4j.rootCategory=INFO,A1
138 log4j.appender.A1=er.extensions.logging.ERXConsoleAppender
139 log4j.appender.A1.layout=er.extensions.logging.ERXPatternLayout
140 log4j.appender.A1.layout.ConversionPattern=%d{MMM dd HH:mm:ss} %$[%#] %-5p %c %x - %m%n
141
142 # Log4j Categories
143 # Here are a few log4j sub-categories that are interesting.
144 # Don't forget that in developement mode this file will get reloaded
145 # everytime it changes, so if you say want to turn adaptor debugging
146 # on in the middle of the app simply set the below category to debug.
147 # Very handy.
148 # Base Category
149 log4j.logger.er=INFO
150
151 {{/code}}
152
153 Standard Log4J stuff. Log4J is bundled into ERJars, and make it sure that you don't have a copy of it in /Library/Java/Extensions or it will conflict with the one from ERJars, especially if the one in /Library/Java/Extensions is older than the one in ERJars.
154
155 {{code}}
156
157 # ERExtensions
158 # Transaction - Switching this to debug will start the sql ouputting.
159 log4j.logger.er.transaction.adaptor.EOAdaptorDebugEnabled=DEBUG
160
161 {{/code}}
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).
164
165 {{code}}
166
167 # Fixes - Turning this on will show all the models that are loaded
168 log4j.logger.er.extensions.fixes.ERSharedEOLoader=INFO
169
170 {{/code}}
171
172 See ERXSharedEOLoader.java in ERExtensions.