hi david, i do not understand where you want to add a hashmap ?
i'm thinking about a real business object (ie. a person) that load only some of it's attributes when it is materialized for the first time. this semi loaded person will be put in the cache. when accessing a not loaded attribute there has to be some feature in the getter to detect that this attribute is not loaded. additionally we need to load the full person, that means we have to know which broker or transaction or whatever materialized this object. if you have a simpler solution or even a patch for ojb, please let me know. jakob ----- Original Message ----- From: "David Corbin" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Thursday, September 05, 2002 5:04 PM Subject: Re: AW: Proxy question > [EMAIL PROTECTED] wrote: > > >hi, > > > > > > > >>Well, you can make setting of ANY attribute complete the loading. Then > >>I don't think that would be a problem. > >> > >> > > > >well it requires to have an ojb specific state in the business object and > >also requires modifications of getters and setters. > >another thing i'm thinking about is who loads the object ? > > > > > I'm thinking of a different solution. Currently, dynamic proxy is > handled with java.lang.reflect.Proxy. I don't see why this has to be > any different. Simply add hash map to hold your properties and their > values. > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
