Yep, just imagine a third party library that exports a Tapestry service as web service. Usually these libraries are scanning the classpath and identify objects marked with certain annotations.
I had this issue last week when integration Spring Integration [1] with Tapestry IoC. I think that copying annotations with javassist is sufficient. [1] http://www.springsource.org/spring-integration On Fri, May 21, 2010 at 1:05 AM, Thiago H. de Paula Figueiredo < [email protected]> wrote: > On Thu, 20 May 2010 19:36:58 -0300, Howard Lewis Ship <[email protected]> > wrote: > > What if ServiceResources implemented new methods to gain access to >> annotations (that would be a merge of interface annotations and >> implementation class annotations). >> > > It's far from enough. Anything that uses reflection to get annotations > wouldn't work. ServiceResources would only be useful for for > Tapestry-IoC-based code. > > -- > 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] > > -- Best regards, Igor Drobiazko http://tapestry5.de/blog
