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.
---- Baiss Eric Magnusson Cascade Web Design <http://www.CascadeWebDesign.com>
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
