On Jun 5, 2006, at 2:06 PM, Carter Wojcik wrote:
Thanks for the thoughts and ideas about using
controllers.
From your messages it seems like it is best to stick
with wocomponents for a code screen that contains a
list/search area along with an edit area containing
actions such as save, revert, delete.
When using wocomponents are you still able to do
unittesting for the components? Or do you have java
only classes that contain your logic for testing?
My approach is to follow the unit testing dictum "test everything
that could possibly break" and keep my components so simple that they
could not possibly break. egro, no need to have unit tests for
them. The only code in your component should be directly and
exclusively related to driving the display in the HTML. No fetching,
no (or usually not) sorting, no playing around. That keeps the Java
pretty darn simple, just some glue between the EOs/model and the
view. I have always looked at the .wod/.java combination as the
controller, with the .html as the view and the EOs as the model. But
MVC means a lot of different things to different people and you can
see it in several different ways in WO. I think it is more important
to keep separation of concerns as your focal point and not worry too
much about seeing some form of MVC purity.
Chuck
--
Coming sometime... - an introduction to web applications using
WebObjects and Xcode http://www.global-village.net/wointro
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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
