You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2010/09/01 17:44:07 UTC

[jira] Resolved: (OPENEJB-1346) Improve @AccessTimeout annotation processing

     [ https://issues.apache.org/jira/browse/OPENEJB-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Gawor resolved OPENEJB-1346.
----------------------------------

    Resolution: Fixed

Changes committed in revision 990932 and 991061 to ensure the @AccessTimeout annotations are processed just like the @Lock annotations.

The @AccessTimeout processing relies on the old AssemblyDescriptor.getContainerConcurrency() since it can easily express the meaning of annotations than converting and flattening the annotations to ConcurrentMethods.


> Improve @AccessTimeout annotation processing
> --------------------------------------------
>
>                 Key: OPENEJB-1346
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1346
>             Project: OpenEJB
>          Issue Type: Improvement
>          Components: deployment
>    Affects Versions: (trunk/openejb3)
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>             Fix For: (trunk/openejb3)
>
>
> @AccessTimeout annotations need to be processed and handled in the same way as @Lock annotations. Take the following as an example:
> @AccessTimeout(value = 1)
> class Foo {
>   public void foo();
> }
> @AccessTimeout(value = 2)
> class Bar extends Foo {
>   public void bar();
> }
> In this example the inherited method foo() in Bar should have access timeout of 1 ms. 

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