Sounds like you should be using the full JEE stack. We use it along with Shiro security And we have custom menu components ( was very easy to create ) that do what you are trying to do.
On Nov 19, 2012, at 11:45 AM, "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. Is there a workaround? Can I just > put the annotaions on my DAO Impl classes for example? > > John --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
