Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Seeking Advice for Getting Started

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Seeking Advice for Getting Started

Subject: Re: Seeking Advice for Getting Started
From: Arturo Perez <email@hidden>
Date: Thu, 09 Feb 2006 09:21:24 -0500

John Shepherd wrote:

John Shepherd wrote:
2) Does WO seem appropriate for my "hobby project," or would I be biting off more than a professional programmer could comfortably chew?
Ugh, apologies for two messages so close together, but I meant to write: "...would I be biting off more than a NON-professional programmer could comfortably chew?"

Welcome and a suggestion and a coupla caveats. Suggestion first. If you're interested in not getting a Mac (can't imagine why they're great) then you could probably pick up an old copy of WebObjects that's Windows-compatible from eBay or similar. If you do decide to go the Mac route then a Mini is perfectly adequate for developing WO apps. Just max out the memory and you'll be fine.

Caveats: Some people think in foreign keys, stored procedures, declarative SQL, etc. These people have an almost insurmountable obstacle to learning WO. WO is all about turning the RDBMS artifacts into Objects so that they play better in the O-O world.

Many people think of a WebObjects EnterpriseObject (or EO) as an RDBMS table (i.e., one-to-one mapping between EO and table). In this view, each attribute of the EO corresponds to a column of the table. This latter view, while not 100% wrong, completely misses the boat. An EO is intended to provide a more natural representation for the data than a simple EO-to-table mapping would provide. So, an EO can be a subset of the rows in a table and is often a subset of the columns of a table.

In this vein, you should really start with your Objects and use EO to create the RDBMS (at least conceptually). Let's take your hobby project as a starting point.

You have Song, Artist, RecordLabel, Album. A RecordLabel has the attributes name, catalog (the collection of all the albums they have the rights to), maybe artists (the artists they do business with). Song has title, and album it appears on. Artist has name, albums.

How the preceding looks in an O-O world is somewhat different than how it appears in the RDBMS. WebObjects bridges that gulf.

Personally speaking, I love developing with WO. It feels more natural than many of the alternatives I've tried (ColdFusion, Perl, J2EE, C). -arturo _______________________________________________ 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 References: >Seeking Advice for Getting Started (From: John Shepherd <email@hidden>) >Re: Seeking Advice for Getting Started (From: John Shepherd <email@hidden>) Prev by Date: Re: NSFormatter usage Next by Date: Re: XCode Expressions during debugging Previous by thread: Re: Seeking Advice for Getting Started Next by thread: Re: Seeking Advice for Getting Started Index(es): Date Thread