Nested Beans and Design Question

["Struts Newsgroup (@Basebeans.com)" <st...@basebeans.com>]

Subject: Nested Beans and Design Question
From: Matt Raible <ma...@raibledesigns.com>
 ===
I have the following structure in my application

CourseForm
    -- TopicForm
        -- PageForm
            -- AssetForm


Where a CourseForm has an ArrayList of TopicForms, TopicForm has an
ArrayList of PageForms, etc.

I'm wondering what the suggested design is:


Option 1:
Populate everything on the first request - and keep it in the session.

Option 2: 
Populate the CourseForm on the first request, and only populate the others
with Id's, rather than entire forms.

Option 3:
Only hold the courseId in the session, and look up information in each page
as it's requested.


There might be other options - feel free to add.

Basically, the first time a course is requested, I will have to look up the
first topic, the first page, and the assets in that page.  So at first
request, I will need all this "first" information.

Any tips or ideas are appreciated.

Thanks,

Matt


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>