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: Owen McKerrow <email@hidden>
- Date: Wed, 14 May 2008 14:44:15 +1000
What about something on WOOgnl ?
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - -
"As of tomorrow, employees will only be able to access the building
using individual security cards. Pictures will be taken next
Wednesday employees will receive their cards in two weeks."
- "Dilbert Quotes" Winner, Fred Dales, Microsoft Corp
On 14/05/2008, at 1:59 PM, Chuck Hill wrote:
Hi All,
I wanted to solicit some ideas and suggestions for this session.
My current thought is to have a selection of practices which I will
present and then get comments (debate) from the other members of
the panel. The idea being that we don't all see them with the same
eyes and some of them are likely to provoke some spirited
discussion (not to mention the obligatory "If you are using
Wonder..." comments). I'd like to think of them as "Quite Good"
rather than "Best" practices. I'll leave some time at the end for
audience questions.
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
- check for null in awakeFromInsertion (mostly a JavaClient issue)
- avoid EOAccess classes in your EO methods
- 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
Things that are best practices, but can't be covered properly:
- use Wonder
- use source control
- use log4j
- unit testing (TestNG or JUnit)
- functional testing (Selenium)
Chuck
--
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:
40uow.edu.au
This email sent to email@hidden
_______________________________________________
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