I tend to side with James. Though it seems like something you can quickly pull out of your hat, transaction demarcation in combination with proper connection pooling in web applications is something you'd better get from a well tested, widely used framework rather than suffer from NIH syndrome. Been there, done that, never doing it again.
Though Spring is a giant beast, it is a very nice one shop stop for your connection pooling, datasourcing, hibernate configuring, transaction demarcating problems. Say no to connection leaks: use Spring! Martijn On Tue, Jun 9, 2009 at 4:48 PM, James Carman<[email protected]> wrote: > On Tue, Jun 9, 2009 at 10:44 AM, Martin > Makundi<[email protected]> wrote: >> Well, the executors themselves sure Start and Stop differently, but >> they can use same invocations for starting/stopping the entitymanagers >> (actually: in the discussed example the hooks used in Wicket are from >> EntityManagerUtils -class and they are the only hooks available even >> if hooking from an Executor). > > I mean you can't use the beginRequest/endRequest stuff from Wicket to > demarcate your transactions when you're doing things asynchronously. > It's not a hard problem to solve by any means, but it is something you > must address. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
