Re: Merits of D2JC (was: user obstacles to WOLips adoption (was: Apple's Support of WebObjects))
Re: Merits of D2JC (was: user obstacles to WOLips adoption (was: Apple's Support of WebObjects))
- Subject: Re: Merits of D2JC (was: user obstacles to WOLips adoption (was: Apple's Support of WebObjects))
- From: Andrus Adamchik <email@hidden>
- Date: Mon, 14 May 2007 09:25:08 +0300
On May 9, 2007, at 4:36 PM, David Avendasora wrote:
But, with all that said, note I said "quickly mock-up and
prototype". D2JC is a great tool to make sure my model is valid and
that the entities and relationships, delete-rules, and optionality
I thought were proper on paper, actually work in practice. If they
don't work (generate exceptions or are just "clunky"), I can make a
change to the EOModel, rebuild and have a new app based on the new
structure _literally_ within seconds without writing/rewriting/
refactoring ANY code. The only thing better than Eclipse's
refactoring tools, is not needing to refactor at all. Once I have
tested and proved the model, it makes web development so much
easier because I can simply concentrate on the logic and the UI.
As an FYI and a bit OT, an architecture similar to D2JC is supported
via Cayenne Remote Object Persistence framework:
http://cayenne.apache.org/doc/remote-object-persistence-guide.html
But alas - we don't deal with the Swing part of the equation, only
with getting your objects, relationships and queries across the wire.
IIRC rapid UI prototyping is still not an option in a Swing land.
Andrus
_______________________________________________
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