On Tue, Aug 26, 2008 at 5:17 PM, James Perry <[EMAIL PROTECTED]>wrote:
> On Sun, Aug 24, 2008 at 4:11 AM, jpswain <[EMAIL PROTECTED]> wrote: > > > > I'm just curious what everyone is using for transaction management. I > have > > been working with Wicket for a while now (and loving it) on a pet project > > that also uses Hibernate and Guice. > > I'm realizing now that I might need/want transactional support for a > couple > > parts of my app. > > I can't comment on Guide as it's not something I've evaluated yet > however I do like some of its idiosyncrasies. I use Spring/Hibernate > as my stack and I find it fits perfectly with Wicket and my domain > models. I personally think Spring offers rich transaction management > with its transaction managers, DAO template classes and generic DAO > exception hierarchy. > > > I don't have any experience with Spring or Java EE or EJB, but have been > > avoiding Spring because of what I have read and seen online with so much > > XML-coding. Is it possible to use spring transaction module by itself > and > > without too much XML? I'd really appreciate hearing what y'all are you > guys > > using for your transactional needs. > > As of Spring 2.5, you can configure your beans with non-evasive, fine > grained annotations. It's declarative transaction model is now > annotation based (as of Spring 2.0) so you can make your methods > transactional using the @Transactional annotation Same here: no experience with Guice, but Spring's @Transactional (with the Connection and TransactionStatus being bound to the current thread etc) is working just great. Also the spring helper-classes for junit (or testng) that rollback your transaction after every test are very convenient. > and it can even be > declared on an interface. Yes, but note this: "The Spring team's recommendation is that you only annotate concrete classes with the @Transactional annotation, as opposed to annotating interfaces. You certainly can place the @Transactional annotation on an interface (or an interface method), but this will only work as you would expect it to if you are using interface-based proxies. " Maarten > The propagation and isolation can also fine > tuned like: > > @Transactional(propagation=Propagation.NOT_SUPPORTED, readOnly=false) > void updateOrderLineQuantities(List<OrderLine> orderLines); > > Read this chapter to understand how Spring does transaction management: > > > http://static.springframework.org/spring/docs/2.5.x/reference/transaction.html > > Best, > James. > > > If anyone has recommendations on where to get started with transactions, > > that would be great too. > > > > Thanks! > > J > > -- > > View this message in context: > http://www.nabble.com/My-Wicket-%2B-Hibernate-project--Transaction-solutions--Java-EE-w--Wicket--tp19127403p19127403.html > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > 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] > >
