This sounds really stupid, but is there any way of disableing lazy loading in self-servicing and use only prefetch paths?
Let me explain why:
I have to extend an old application which uses selfservicing. We use adapter for all projects now, and I like the adapter model so much better than selfservicing but I have too little time to convert the whole thing to adapter.
For our current projects, I've been using a service layer on which most of the BL functionality is defined. These services contain the logic to communicate with the database (using llblgen) and the other BL. The asp.net pages use only these services to fetch/store the entities they need. To be clear: the entities do not (yet) pass a physical tier, it's just a way to achieve better code separation.
Since selfservicing is also able to use prefetch paths, it should be possible to more or less use the same architecture for the old selfservicing application.
But I'm afraid that if other developers (or I myself for that matter ) work on the project, they might not prefetch everything correctly, and if this happens, it will go unnoticed, for any related entity which is not prefetched will be loaded on demand instead.
So is there any way of forcing everything to be prefetched and/or disableing loading on demand?