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:
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 is automatically added to the classpath when you create a new Wonder project.
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.
If set to true, newly created instances use the shared editing context.
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.
Provides automatic inverse relationship updating for ERXGenericRecord and ERXCustomObject.
When to put it at FALSE
If you have a mix of ERXGenericRecords and EOGenericRecords between models, you're better of turning it off.
Since an EOGenericRecords doesn't have the facilities to update the inverse relationship, you will get a ClassCastException.
Those properties, if used, allow you to specify the JDBC/EOF information for all of your models. See Best Practices-Properties Files
Those properties are to enable support for migrations. 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.
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.
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).
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).
Try to use globalIDs to determine the hashCode for EOs.
Check Project WONDER-Frameworks-ERJavaMail for an explanation.
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.
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).
See ERXSharedEOLoader.java in ERExtensions.