|
From: James C. <jim...@do...> - 2005-05-05 13:28:47
|
That's the thread where I described a service layer approach that we = began using when we ditched OSIV. We give our web-tier a service layer to = interact with that defines a transactional boundary. It worked very well for us, except for the problem that Ugo Cei brought = up regarding the ugliness of pre-loading lazy-loaded collections. Not = really a problem, but not so elegant. jim > -----Original Message----- > > There are other workarounds that may be jammed in, but the ones I = can > > think > > up are not exactly elegant. Perhaps this is simply a case of = developer > > beware; a known side-effect to using the OSIV approach to web > development. > > I'd appreciate any advice on whether the framework can be coerced to > > eliminate one of the remaining flaws in this pattern. >=20 > Also take a look at the following discussion, which details more of = the > issues of OSIV: >=20 > = http://www.newsarch.com/archive/mailinglist/comp/java/springframework/use= r > /msg03641.html >=20 > Erwin |