Big Javabean?

Hi There are 2 quick questions. 1) I'm considering making one huge javabean that will have 100+ fields. This bean will be share in the session across up to 23 different screen. I think this is probably the cleanest way, as the same field might show up in different screens. I don't think this

Re: Big Javabean?

--- Poon, Johnny [EMAIL PROTECTED] wrote: Hi There are 2 quick questions. 1) I'm considering making one huge javabean that will have 100+ fields. This bean will be share in the session across up to 23 different screen. I think this is probably the cleanest way, as the same field might

Re: Big Javabean?

Don't think there is a problem with a javabean that size. We have similar sizes. May want to think about using request scope though (with the same java bean). This means more calls to the database however. One question to ask is if you need to have concurrent access to the same data. Your

RE: Big Javabean?

Graham [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2003 9:38 AM To: Struts Users Mailing List Subject: Re: Big Javabean? --- Poon, Johnny [EMAIL PROTECTED] wrote: Hi There are 2 quick questions. 1) I'm considering making one huge javabean that will have 100+ fields. This bean

Re: Big Javabean?

I would disagree with having fine-grained action forms. You will run into problems by splitting them apart for a logicial entity. This is especially true if you have more than one type. JSP re-use is not a problem since this is done by reflection. However form-bean re-use will cause problems