On Mon, Jun 6, 2011 at 9:58 AM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > On Sat, 04 Jun 2011 03:58:41 -0300, Igor Drobiazko > <[email protected]> wrote: > >> Looks like we need to discuss the "copying annotations to proxies with >> plastic" issue again. > > +1 for copying annotations to proxies. This is a huge limiting factor for > Tapestry-IoC. Unfortunately, I don't have the time to investigate it myself, > even being very curious about it.
I went down that route and hit a roadblock of some kind; instead I changed other APIs to expose a mix of annotations from the implementation class (when known) and from the service interface. Perhaps with Javassist/ClassFactory so marginalized now, the roadblock won't be a big issue, but the more we can do using the API, the more comfortable I feel. I've never been happy with exposing the details of the service implementation class to decorators. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
