On Sat, Nov 1, 2008 at 10:15, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > On Fri, Oct 31, 2008 at 6:51 PM, Rickard Öberg <[EMAIL PROTECTED]> wrote: > >>> But if I did uowf.currentUnitOfWork().newUnitOfWork() >> >> This I think is a bug. Currently the nested UoW uses the visibility of >> the original module. It should be the visibility of the module that >> creates it, I think. This takes a bit of trickery to accomplish, but >> it's doable. > > When we discussed this in the office yesterday, I also came to the > conclusion that perhaps the problem lied in 'nested UoW should be able > to have different visibility'. > > uowf.currentUnitOfWork().newUnitOfWork( Module module );
Because of the potential visibility problem. The domain services has no choice to create new unit of work. It has no way of knowing whether it's being invoked from the web layer, or invoked within domain layer. Does this sounds right? Regards, Edward Yakop _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
