[jira] Issue Comment Edited: (TAP5-335) Provide access to annotations of service implementation class

["Ulrich Stärk (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837260#action_12837260 ] 

Ulrich Stärk edited comment on TAP5-335 at 2/23/10 2:49 PM:
------------------------------------------------------------

Another use case where this could come in very handy are webservices. The javax.jws @Webservice annotation can be put on an interface but only without parameters like the serviceName parameter that identifies a service. This has to be on the implementation class and gets lost when creating a proxy around it.

      was (Author: ulrich.staerk):
    Another use case where this could come in very handy are webservices. The JAX-WS @Webservice annotation can be put on an interface but only without parameters like the serviceName parameter that identifies a service. This has to be on the implementation class and gets lost when creating a proxy around it.
  
> Provide access to annotations of service implementation class
> -------------------------------------------------------------
>
>                 Key: TAP5-335
>                 URL: https://issues.apache.org/jira/browse/TAP5-335
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.0.15
>            Reporter: Lubor Gajda
>
> 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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.