You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tapestry.apache.org by John <jo...@quivinco.com> on 2012/11/25 14:57:48 UTC

Re: Tapestry jpa transactions - JIRA TAP5-2029

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 <jo...@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-unsubscribe@tapestry.apache.org
  For additional commands, e-mail: users-help@tapestry.apache.org