Hi again, > > > You don't think having the holy grail would be a best > practice in of itself?
That's why I started OJB ;-) > >So you need a partially loading proxy? > >OK here you go: > >take a look at tutorial3.html: > >http://jakarta.apache.org/ojb/tutorial3.html#using%20proxy%20classes > > > > > I've seen that. I suppose, by adding another > class-descriptor for the > CustomerProxy object, you could load the partial data, and non-loaded > data could continue to proxy the way it "normally does". It just > strikes me as a useful design/approach (maybe not - maybe I > haven't been > bitten enough by proxy problems). Useful enough, that > someway to make a > dynmaic "half-proxy" would have broad appeal. Perhaps not. I guess you are right. The JDO spec even has a concept of a default fetch group. The default fetch group of a class contains all attributes that are loaded immediately. All other attributes are loaded on demand. So I guess we will have such a feature sooner or later. > (I haven't > looked at how dynamic proxies are implemented). > is a very simple delegation mechanism. partial loading witha default fetch will be a bit trickier. cheers, Thomas > >As you can see it is possible to use either dynamic proxies (that are > >generated automatically at runtime) or manually implemented proxies. > >You can provide your own proxy implementation that performs > any kind of > >partial loading. > >You have to tell OJB about this proxy in the > class-descriptor for your > >Customer class: > ><class-descriptor > > class="com.my.Customer" > > proxy="com.my.CustomerProxy" > > table="CUSTOMERS" > > > > > > > >cheers, > >Thomas > > > > > > > > -- > 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]>
