please see/feedback https://issues.apache.org/jira/browse/TAP5-2029 ----- Original Message ----- From: Thiago H de Paula Figueiredo To: Tapestry users Sent: Monday, November 19, 2012 5:48 PM Subject: Re: Tapestry jpa transactions
On Mon, 19 Nov 2012 14:45:48 -0200, John <j...@quivinco.com> wrote: > 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. I don't like that either. > Is there a workaround? I don't think so. > Can I just put the annotaions on my DAO Impl classes for example? Not now. Please post a JIRA for that. I'd love to see this Tapestry-IoC problem fixed too. -- Thiago H. de Paula Figueiredo --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
