Re-Suggestions for Best Practices session at WOWODC
Re-Suggestions for Best Practices session at WOWODC
- Subject: Re-Suggestions for Best Practices session at WOWODC
- From: Baiss Eric Magnusson <email@hidden>
- Date: Wed, 04 Jun 2008 09:58:43 -0700
I like the below:
Some ideas for inclusion are:
- using EOPrototypes
- use of peer and nested editing contexts and the then needed locking
of editing contexts
- generate your EOs and use the Generation gap pattern (though with
Entity modeler, you have to fight to not do this)
- use generation to create common worker methods
- generate String constants to avoid hard coding attribute and
relationship names
- use qualifiers objects rather than qualifierWithFormat
- use stateless components and store state in the page
- handling checked exceptions with NSForwardException
- keep WOComponent Java files focused on the UI
- watch the generated SQL (for batch fetching and optimization index
needs)
- using formatters for reusability
- don't repeat yourself, use common build files
- block direct page requests
- use class name to create component
- plan to handle errors from saveChanges()
- use custom EOGenericRecord subclass
- use embedded frameworks
PS: I'm staying at the Baldwin, and taking the AlaskaAir, Seattle, Friday, flight to SFO, arrival time 6:44PM.
|
_______________________________________________
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