Re: Inherited Relationships using Different Destinations
Re: Inherited Relationships using Different Destinations
- Subject: Re: Inherited Relationships using Different Destinations
- From: Chuck Hill <email@hidden>
- Date: Fri, 5 Sep 2008 15:16:57 -0700
On Sep 5, 2008, at 2:23 PM, David Avendasora wrote:
On Sep 5, 2008, at 2:52 PM, Florijan Stamenkovic wrote:
I mean, I doubt you can get your GUI to recognize all the
overriding you did in the model anyway,
Well, with Direct to Java Client it's _all_ about what the Model
says. Right now, if I say I want to open the destination object of a
relationship that I know is ManufacturedBatch, it looks at the Model
and says "Well, according to the destination of the relationship,
this is a LotCode, so I'm going to give you the LotCode UI" Same for
Adding a ManufacturedBatch to the relationship, it's going to allow
me to pick from any subclass of LotCode because that's what the
Model says.
If the model were pointing to ManufacturedBatch as the destination
Entity, I'd get the ManufacturedBatch UI for opening, searching and
creating instead.
That makes an even stronger case for NOT modeling this on the abstract
parent. Put it in the Java class for the interface, but don't model it.
so at some point in the GUI you need to remove unacceptable choices
so the user can not screw up,
D2JC does this for me, if the Model is right. This is one of the
things that I really LOVE about D2JC. It really points out
weaknesses in your model. Things that you might otherwise solve with
code it pushes you to solve in the Model.
and if you do that, well, then you might as well put a hard-core
stop on any mistake by throwing an exception.
That is a good idea. Who knows what UI the next guy is going to slap
on my foundation. Maybe a web app. (shudder)
What you are doing now seems incredibly more complicated, and less
secure really.
I think you are absolutely correct when you are creating the UI by
hand, but I think the opposite is true as long as D2JC is TCOB.
It was a nice thought though. Really, really out there...
Now I _really_ want to make it work... ;-)
Chuck, Flor, everyone, thanks for your input on this. It has really
made me think hard about if this is the right thing to do or not.
It's not. :-P
Chuck
--
Chuck Hill Senior Consultant / VP Development
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:
This email sent to email@hidden