Re: Better start with Wonder than WO
Re: Better start with Wonder than WO
- Subject: Re: Better start with Wonder than WO
- From: Chuck Hill <email@hidden>
- Date: Thu, 20 Mar 2008 13:56:18 -0700
On Mar 20, 2008, at 1:48 PM, Art Isbell wrote:
On Mar 20, 2008, at 10:34 AM, David LeBer wrote:
On 20-Mar-08, at 4:27 PM, Gustavo Pizano wrote:
:( now im lost.
GUS
PS: what would be the reason for using wonder?
Short list?:
Ajax.framework - Ajax the WebObjects way
ERXGenericRecord - will* methods plus much much more
Auto EOEditingContext locking
ERMigrations - Easy database schema change managment
ERPrototypes - Consistent set of Prototypes for many databases
Validity - Model based validation
ERDirectToWeb - Lots of extra stuff for D2W applications
ERTaggable - Tagging mixin for WebObjects apps
ERAttachment - Attachment mixin for WebObjects apps
ERJavaMail - WO wrapper around Javamail
Any number of things in ERXExtensions
Please correct me if I'm wrong, but isn't Gustavo's goal to compare
WO with other Web development technologies as part of a computer
science course? How much can a student expect to learn while also
spending time for other classes as well? WO itself is huge. Add
WOnder on top of that and I think you'll be guaranteeing the Gustavo
doesn't finish his assignment by the end of his course. I mean, how
much of the above short list will Gustavo actually need in the next
few months?
IMHO
Auto EOEditingContext locking
ERPrototypes - Consistent set of Prototypes for many databases
I think expecting a WO newby to learn WO plus WOnder concurrently
may be enough to drive some newbies to other technologies. I'm a
proponent of the KISS principle wherever possible; e.g., learn WO
basics first, then add WOnder when you understand WO basics.
Art, I think you are missing the point. Create a new Wonder app in
WOLips. That is it. That is all that you _need_ to learn to
benefit. The app has a properties file (see below) that turns on the
benefits. You can edit the properties if you do need mail or
something. But you don't have to worry about EC locking etc. Don't
do this, and _then_ how much do you need to know?
Chuck
# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true
# EOF
er.extensions.ERXApplication.useEditingContextUnlocker=true
er.extensions.ERXEC.defaultAutomaticLockUnlock=true
er.extensions.ERXEC.useSharedEditingContext=false
er.extensions.ERXEC.defaultCoalesceAutoLocks=true
er.extensions.ERXEnterpriseObject.applyRestrictingQualifierOnInsert=true
# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel
# Repetition Fixes
#er.extensions.ERXWORepetition.checkHashCodes=true
#er.extensions.ERXWORepetition.raiseOnUnmatchedObject=true
# Mail
er.javamail.centralize=true
er.javamail.adminEmail=email@hidden
er.javamail.debugEnabled=false
er.javamail.milliSecondsWaitIfSenderOverflowed=6000
er.javamail.smtpHost=your.smtpserver.com
er.javamail.smtpAuth=false
er.javamail.smtpUser=
er.javamail.smtpPassword=
# Log4j Configuration
log4j.loggerFactory=er.extensions.ERXLogger$Factory
# Set root category priority to DEBUG and its only appender to A1.
log4j.rootCategory=DEBUG, A1
# A1 is set to be a FileAppender which outputs to System.out.
log4j.appender.A1=org.apache.log4j.ConsoleAppender
# A1 uses PatternLayout.
log4j.appender.A1.layout=er.extensions.ERXPatternLayout
log4j.appender.A1.layout.ConversionPattern=%d{MMM dd HH:mm:ss} %$[%#]
(%F:%L) %-5p %c %x - %m%n
# Note that (%F:%L) is fairly slow and shouldn't be used in
performance intensive logging
# The above pattern will produce logs that look like:
# Jun 18 17:46:18 MyAppName[4002] (MyClassFile.java:40) INFO
er.foo.MyCategory - Some log
# Custom Categories - These are the main categories and sub categories
# that are used in frameworks.
# Base Category
log4j.logger.er=INFO
# Here are a few log4j sub-categories that are interesting.
# Don't forget that in developement mode this file will get reloaded
# everytime it changes, so if you say want to turn adaptor debugging
# on in the middle of the app simply set the below category to debug.
# Very handy.
# ERExtensions
# Transaction - Switching this to debug will start the sql ouputting.
log4j.logger.er.transaction.adaptor.EOAdaptorDebugEnabled=DEBUG
# Fixes - Turning this on will show all the models that are loaded
log4j.logger.er.extensions.fixes.ERSharedEOLoader=INFO
er.extensions.ERXNSLogLog4jBridge=INFO
#log4j.logger.er.eo.ERXGenericRecord=DEBUG
#log4j.logger.er.validation.ERXEntityClassDescription=DEBUG
#log4j.logger.er.default.ERXEntityClassDescription=DEBUG
log4j.logger.er.extensions.ERXDatabaseContextDelegate=WARN
log4j.logger.er.extensions.ERXConfigurationManager=INFO
#log4j.logger.er.extensions.ERXApplication.RequestHandling=DEBUG
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden