Hi Borislav,
yes, this is actually one big part of my problem: sometimes I'll need
collections A and B of an object and sometimes no collections at all or
different collections.
How does your business layer represent this? Do you have one method in
which you specify the attributes that are needed or do you have multiple
methods?
The problem that I see is that with any approach, you kind of couple
view and model very closely but I assume this cannot be helped.
Tom
Borislav Sabev wrote:
Tom Ziemer wrote:
Hi Borislav,
unfortunately I cannot do this, because I have a rich client and a
(struts-based) web frontend. Consequently, my business layer must load
and initialize all dom objects that are requested, because I cannot
have an open session on my rich client that is using web services to
communicate with the app.
Thanks,
So why do you use any lazy initialization at all if you allways have to
load the whole object graph in one request?
Anyway I think I know what you mean - in same cases you don't need the
whole graph (i.e. the benefit of LazyInitialization), in some other -
you need it (thus, you don't need lazy initialization). I handle this in
case-by-case basis - i.e. when I need the whole graph, I load it
explicitely.
If this can help you ....
Borislav
---------------------------------------------------------------------
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]
