Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: struts-user@jakarta.apache.org
Message-ID: <3B8BDC25.2070602@netmeme.org>
Date: Tue, 28 Aug 2001 12:00:05 -0600
From: Bryan Field-Elliot <bryan_lists@netmeme.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3+) Gecko/20010825
MIME-Version: 1.0
To: struts-user@jakarta.apache.org
Subject: Re: Performance, Reflection, and Object Creation vs. Cacheing
References: <3B8B17EA.20501@netmeme.org> <3B8BA07E.E7A9A707@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Thanks for the insights Ted,

Please help me if I'm misinterpreting. But looking at your code, it 
seems like your "populate" still takes a plain Bean as it's destination, 
although it can use a property set (in this case, a ResultSet) as the 
source. This reduces the proliferation of Value (or other Bean) classes 
by 50%, but not 100%. In your scenario, which set of beans still need to 
be developed as plain old beans rather than dynamic sets of properties 
(e.g. the Entity beans, the Value Objects, or the Struts Form Beans, etc?)?

Thanks,
Bryan


Ted Husted wrote:

>
>    public static void populate(Object bean,
>                                ResultSet resultSet)
>