Hi- Are you using these VOs just to populate fields on JSP pages and pass information to Struts actions? If so, there will be no serialization all as JSP generation is done server-side, and all the VO instances will be in the same JVM, so nothing goes across the wire to the client web browser.
The only way you might have serialization is if you are storing these VOs as session or application variables, and you have a cluster of web servers that maintains session state between all servers so that a given user's requests can be serviced by any web server node in the cluster. -ed On 6/19/05, Yaakov Chaikin <[EMAIL PROTECTED]> wrote: > Hi all, > > I have the following situation. I have a Vo model that is in essence a > domain/business object model. Of course, a particular screen doesn't > need the entire model to be loaded with data. So, what I was thinking > is > 1) Make all class variables objects (as opposed to primitives, most > are objects anyway) > 2) Make all class variables NULL, unless I need it for a particular screen. > > This way, I won't have to carry data around the wire that I don't need. > > The question I have is this. What performance hit, if any, do I get by > passing around an object with null pointers in it? How do they get > serialized? > > Is this a good idea in general or am I just imagining that passing > around null pointers saves me "THAT MUCH"? > > Thanks, > Yaakov. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
