In the tapestry jpa docs we are instructed to provide annotations to manage transaction commitment into the DAO interface classes, e.g.
@CommitAfter @PersistenceContext(unitName = "DemoUnit") void add(User user); I'm not liking this much as I don't want to explose details of the implementation in my service interfaces. Is there a workaround? Can I just put the annotaions on my DAO Impl classes for example? John