While that is true, most MVC I have seen use separate POJO for view- controller communication, like an javabean or an action bean in Struts. Generally these are simpler, disconnected objects. But if you didn't separate the view and controller well, your view layer would have to worry about transactions as well, correct.
Ryan On Jan 12, 2010, at 10:39 AM, Raul Raja Martinez wrote: > In a MVC approach, if your view renders part of the model wouldn't > you get > exceptions unless you fully initialize view objects from the node > values? I > mean if your view objects depend on the node on any way to render, the > render phase would be outside the transanctional scope. This is the > same > issue you find with hibernate with LazyInitExceptions when you call > to read > outside of a session. > > On Jan 12, 2010 2:28 AM, "Mattias Persson" <[email protected]> > wrote: > > Your code doesn't need to be littered with transaction management. You > can have a very big MVC (Model-View-Controller) application or > something like that and _only_ have transaction handling in one > place... in the Controller. > > See http://wiki.neo4j.org/content/Transactions#Best_practices (page > under construction) > > 2010/1/12 Laurent Laborde <[email protected]>: > >> On Tue, Jan 12, 2010 at 6:41 AM, Ryan Levering <[email protected]> > wrote: >> >> 1. User.getName... > -- > Mattias Persson, [[email protected]] > Neo Technology, www.neotechnology.com > > _______________________________________________ Neo mailing list > [email protected] https://lists.... > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
