On Jun 25, 2006, at 2:41 PM, Andrew Madu wrote:
Hi,
I am planning on migrating an existing cocoon
framework/hibernate/postgreSQL
project over to webobjects framework. Can anyone please tell me what
possible benefits I would get from employing webobjects in terms of:
1. MVC (Continuations)
2. Persistence (mapping)
3. Seperation of concerns (seperation of logic from design)
Does webojects make use of XML/XSLT as cocoon does? Is it possible to
re-engineer my postgreSQL tables to persistent weboject objects ala
hibernate mapping? What is the best reference material to purchase for
webobject beginners like myself?
Many thanks for all of your help in advance
Andrew
Well, you don't say why. These are off the cuff so ...
1. MVC WebObjects helps a lot with doing good (not perfect) MVC. It
encourages the use of webpages as views with little to no logic in
them, it gives a very good fromework for creating models that are
internally consistent and the controllers provided are cleanly
engineered with over 10 years of design and practical experience behind
it.
2. WebObjects persistence mapping is second only to TopLink (now an
Oracle product) and even that's debatable. Hibernate's persistence
does not compare. For a sense of the difference compare Torque to
Cayenne. The relative difference between WebObjects/EOF and Hibernate
is comparable.
3. See #1.
-arturo
_______________________________________________
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 archive@mail-archive.com
