[TAP5-335] Provide access to annotations of service implementation class

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.15
• Fix Version/s: 5.2.0
• Component/s: tapestry-ioc
• Assignee: Igor Drobiazko
• Reporter: Lubor Gajda
• Created: 06/Nov/08 22:41
• Updated: 14/Nov/10 13:51
• Resolved: 28/Jul/10 06:42

Description

In some situations it would be useful to have direct access to annotations of service implementation class. This would allow us, during registry startup, detect services with some specific class or method level annotations and take related actions.

For instance imagine tapestry-quartz integration based on simple declarative
mechanism where it would be possible to use something like this:

public class MyServiceImpl implements MyService {

@Scheduled(cronExpression="0/5 * * * * ?")
public void myMethod()

{ ... }

}

and framework would be able, during registry startup, automatically detect all service methods annotated by @Scheduled annotation and register them in the scheduler.

I see two possible solutions:

1. Modify ServiceDef to hold information about service implementation class.

2. Service proxy could inherit all annotations from service implementation
class, then we would be able to check annotations directly on service proxy.

But maybe there is another, more elegant solution.

For more details see thread:
http://thread.gmane.org/gmane.comp.java.tapestry.user/67116/focus=67116

Issue Links

• relates to: TAP5-1349 The method parameter annotations are missing from Tapestry IoC proxies