You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2009/08/03 10:01:18 UTC
[jira] Commented: (FELIX-1440) Abort method (binder, activator)
method search on non-accessible suitable methods
[ https://issues.apache.org/jira/browse/FELIX-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738220#action_12738220 ]
Felix Meschberger commented on FELIX-1440:
------------------------------------------
In Rev. 800244: Add SuitableMethodNotAccessibleException to support method lookup termination if a class provides suitable methods which are not accessible. Plus test case in BindMethodTest
> Abort method (binder, activator) method search on non-accessible suitable methods
> ---------------------------------------------------------------------------------
>
> Key: FELIX-1440
> URL: https://issues.apache.org/jira/browse/FELIX-1440
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.2.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.2.0
>
>
> The R4.2 draft specification (dated 2009/03/10) states in section 112.8.4, Locating Component Methods:
> If suitable methods are found in a class but none of
> the suitable methods are accessible, the search for suitable methods terminates
> with no suitable method having been located. If no suitable methods
> are found in a class, the search continues in the superclass.
> This means, that as soon as a class would have one or more suitable methods but none of these is accessible, the search should terminate with no method found.
> Currently the search continues as if no suitable method would have been found if suitable methods found are not accessible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.