• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Interfaces and Java Client
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Interfaces and Java Client


  • Subject: Re: Interfaces and Java Client
  • From: David Avendasora <email@hidden>
  • Date: Fri, 28 Apr 2006 06:03:21 +0100

I am using inheritance in the model as well as interfaces but the problem isn't the inheritance! I'm having a hard time explaining the structure of my application so I've done my first-ever UML Class Diagram to try to explain it better. I've attached it - hopefully it makes it.

I don't think I'm doing anything crazy. I think it is pretty standard OO stuff (straight out of Head First Design Patterns). Can anyone tell me a better structure?

Dave

GIF image


On Apr 27, 2006, at 6:10 PM, Ken Anderson wrote:

Inheritance can vastly improve the features of EOF if used properly. In general, I usually make all super-entities abstract, and have a different table for each leaf. However, if your data is all the same and you just need inheritance for different behavior in code, I typically use a single table and use well defined qualifiers for the entities. A while ago (after much complaining), the EOF engineers worked out a way to not do queries for all the sub-entities if you're entity qualifier was straightforward like: "type = 'A'". I highly suggest sticking with this for performance reasons.

Ken

On Apr 27, 2006, at 1:00 PM, Chuck Hill wrote:


On Apr 27, 2006, at 1:13 AM, Paul Lynch wrote:

You may want to use entity inheritance to design your model; see http://developer.apple.com/documentation/WebObjects/ UsingEOModeler/7ModelingInheritance/chapter_7_section_1.html

The only thing I'll add is that, from experience, most of the times that using inheritance is possible, I choose to flatten out the model instead. Other people may have different experiences. From the OO viewpoint, a complex design has the same problems as overnormalisation has in relational database design.

On the other side of this fence, I use inheritance whenever it makes sense in the OO view. I have found that this greatly simplifies many aspects of the application.

Chuck

--
Coming in late 2006 - 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@hidden)
Help/Unsubscribe/Update your Subscription:
40anderhome.com


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:
40avendasora.com


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

  • Follow-Ups:
    • Re: Interfaces and Java Client
      • From: Chuck Hill <email@hidden>
    • Re: Interfaces and Java Client
      • From: Paul Lynch <email@hidden>
    • Re: Interfaces and Java Client
      • From: Ian Joyner <email@hidden>
References: 
 >Re: Interfaces and Java Client (From: David Avendasora <email@hidden>)
 >Re: Interfaces and Java Client (From: Paul Lynch <email@hidden>)
 >Re: Interfaces and Java Client (From: Chuck Hill <email@hidden>)
 >Re: Interfaces and Java Client (From: Ken Anderson <email@hidden>)

  • Prev by Date: Re: Switch Component question...
  • Next by Date: Re: Problem loading the D2W assistant
  • Previous by thread: Re: Interfaces and Java Client
  • Next by thread: Re: Interfaces and Java Client
  • Index(es):
    • Date
    • Thread