Mixing transaction management styles
I think Andy knows about the "requires new" transaction semantics; I think he's asking whether it's OK to mix transaction declaration styles, i.e. have some of your transactional behaviour defined using classic CMT and the rest defined using Spring's PlatformTransactionManager API (as per the reference guide, e.g. via @Transactional annotations and so on).
I certainly hope this approach is OK, because I'm using it on a live app!
"Now is the EJB of our discontent made glorious Spring"