Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Wed, 4 Apr 2012 09:08:28 +0000 (UTC)
From: =?utf-8?Q?Johan_Str=C3=B6m_=28Created=29_=28JIRA=29?= <jira@apache.org>
To: dev@felix.apache.org
Message-ID: 
 <910938485.10824.1333530508996.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (FELIX-3430) SCR Modified annotation required,
 default method is not used.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

SCR Modified annotation required, default method is not used.
-------------------------------------------------------------

                 Key: FELIX-3430
                 URL: https://issues.apache.org/jira/browse/FELIX-3430
             Project: Felix
          Issue Type: Bug
            Reporter: Johan Str=C3=B6m
            Priority: Minor


>From http://felix.apache.org/site/scr-annotations.html:

{quote}
Activate, Deactivate, and Modified
The Declarative Service version 1.1 allows to specify the name for the acti=
vate, deactivate and modified method (see the spec for more information). T=
he Activate, Deactivate, and Modified annotation can be used to mark a meth=
od to be used for the specified purpose. However, as the DS specifies a met=
hod search algorithm, there are rare cases where the marked method is not u=
sed (if there is another method with the same name, but a different signatu=
re this might happen).
{quote}


This holds true for activate and deactivate. However, for modified, it does=
n't seem to work without explicitly declaring it so in the scr:component ma=
nifest.=20
Looking at impl/manager/ImmediateComponentManager.java, activate & deactiva=
te is not handled the same way as modified:
{code}
    private boolean modify() {
...
        // 1. no live update if there is no declared method
        if ( getComponentMetadata().getModified() =3D=3D null )
        {
            return false;
        }
{code}

Thus, if not defined at all, it is not used. And that seems to be against t=
he spec.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira