As I remember it, I changed the API so that a search for an annotation on a service will also check the service implementation ... so rather than "copy" the annotations (which is very, very problematic), the code looks into two places. Take a peek at implementations of AnnotationProvider.
On Fri, Jun 28, 2013 at 1:37 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > Oops, now I realized my suggestion was written in a bad way. It's about > Tapestry-IoC services, not Tapestry(-core). > > What I'm actually suggesting is beyond that: it's about copying the > annotations on service implementation *methods* to their corresponding > methods in the service proxy. This would solve the problem described by > John. This cannot be solved in any other way in Tapestry-IoC right now. > > > On Fri, 28 Jun 2013 16:51:40 -0300, Howard Lewis Ship <hls...@gmail.com> > wrote: > > Yes, but it is optional. Anything you don't want to specify using an >> annotation on the interface can be specified instead using the >> ServiceBinder interface, or as an annotation on a module method. >> >> Ok, in this case, if you want to use the Tapestry-specific magic, you get >> to use the Tapestry-specific annotation. >> >> If you don't like that, you can inject the underlying JPASessionManager >> service and get/commit the transaction yourself. Or create a >> Tapestry-facing Facade with the Tapestry annotations whose implementation >> delegates to the "vanilla" interface. >> >> >> On Fri, Jun 28, 2013 at 6:27 AM, Thiago H de Paula Figueiredo < >> thiag...@gmail.com> wrote: >> >> On Thu, 27 Jun 2013 06:05:14 -0300, <no-re...@comments.apache.org> >>> wrote: >>> >>> Hello, >>> >>>> John has commented on http://tapestry.apache.org/** >>>> integrating-with-jpa.html<http**://tapestry.apache.org/** >>>> integrating-with-jpa.html<http://tapestry.apache.org/integrating-with-jpa.html> >>>> > >>>> >>>> . >>>> You can find the comment here: >>>> http://tapestry.apache.org/****integrating-with-jpa.html#**** >>>> comment_1410<http://tapestry.apache.org/**integrating-with-jpa.html#**comment_1410> >>>> <http://tapestry.**apache.org/integrating-with-**jpa.html#comment_1410<http://tapestry.apache.org/integrating-with-jpa.html#comment_1410> >>>> > >>>> >>>> Please note that if the comment contains a hyperlink, it must be >>>> approved >>>> before it is shown on the site. >>>> >>>> Below is the reply that was posted: >>>> ~~~~ >>>> Adding implementations specific annotations to the service interfaces >>>> breaks the interface/implementation independence. >>>> ~~~~ >>>> >>>> >>> I agree with this. What do you guys think? I think this is a serious >>> shotcoming in Tapestry-IoC. >>> >>> -- >>> Thiago H. de Paula Figueiredo >>> >>> ------------------------------****----------------------------** >>> --**--------- >>> To unsubscribe, e-mail: >>> dev-unsubscribe@tapestry.**apa**che.org<http://apache.org> >>> <dev-unsubscribe@**tapestry.apache.org<dev-unsubscr...@tapestry.apache.org> >>> > >>> >>> For additional commands, e-mail: dev-h...@tapestry.apache.org >>> >>> >>> >> >> > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@tapestry.**apache.org<dev-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: dev-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
