| Hi, John, On Feb 3, 2006, at 2:04 PM, John Huss wrote:
I've done it, but, by and large, it's easier with two separate pages. If you keep both on one page, you'll generally find that your detail list size changes dynamically and that has to be controlled carefully so you don't fall prey to the change-of-WO-template-in-the-middle-of-the-Request-Response-Cycle problem. This problem has cropped up and been posted to the list several times. Here is a description of the problem and its source in response to another list correspondent last summer. Note the last paragraph of the response where the problem is described. Read that first and you'll better understand what precedes it. If you build two pages around WODisplayGroups, you can simply drag-and-drop the entity of the master and the relationship to the detail from the EOModel to your respective pages and have a lot of this infrastructure built for you quickly. Regards, Jerry -- __ Jerry W. Walker, WebObjects Developer/Instructor for High Performance Industrial Strength Internet Enabled Systems jerrywwalker@gee-em-aye-eye-ell.com 203 278-4085 office |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
