[jira] Updated: (FELIX-925) Extend SCR to allow alternate activate and deactivate method signatures
[ https://issues.apache.org/jira/browse/FELIX-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-925: Assignee: Felix Meschberger > Extend SCR to allow alternate activate and deactivate method signatures > --- > > Key: FELIX-925 > URL: https://issues.apache.org/jira/browse/FELIX-925 > Project: Felix > Issue Type: New Feature > Components: Declarative Services (SCR) >Affects Versions: scr-1.0.6 > Environment: OSGi RFC-0134, OSGi R4.2 Early Draft 2 > (http://www.osgi.org/download/osgi-4.2-early-draft2.pdf) >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: scr-1.2.0 > > > A way is needed to avoid using DS API at all in components with SCR. This > means the activate and deactivate methods should not require the > ComponentContext parameter. We should also allow the names of the activate > and deactivate methods to be specified to avoid requiring specific method > names. > To support this, the follow attributes will be added to the component element: > /> > > The activate attribute will specify the name of the activate method and the > deactivate attribute will specify the name of the deactivate method. > The signature for the activate and deactivate methods is: > p r o t e c t ed vo i d (< a r gumen t s > > ) ; > can be zero or more arguments. > For the activate method each argument must be of one of the following types: > ● ComponentContext - the Component Context for the component > ● BundleContext - the Bundle Context of the component's bundle > ● Map - the Component Properties from ComponentContext.getProperties. > If any argument of the activate method is not one of the above types, SCR > must log an error message with the Log Service, if present, and the component > configuration is not activated. > For the deactivate method each argument must be of one of the following types: > ● int/Integer - the deactivation reason > ● ComponentContext - the Component Context for the component > ● BundleContext - the Bundle Context of the component's bundle > ● Map - the Component Properties from ComponentContext.getProperties. > If any argument of the deactivate method is not one of the above types, SCR > must log an error message with the Log Service, if present, and the > deactivation of the component configuration will continue. > The methods may also be declared public. The same rules as specified in > 112.5.8 will be used to locate the activate and deactivate methods in the > implementation class hierarchy. > 3.2.1 Component deactivation reasons > When a component is deactivated, the reason for the deactivation can be > passed to the deactivate method. The following deactivation reasons are > specified in ComponentConstants. > /** >* The reason the component instance was deactivated is > unspecified. >* >* @since 1.1 >*/ > public static final int DEACTIVATION_REASON_UNSPECIFIED = 0; > /** >* The component instance was deactivated because the > component was disabled. >* >* @since 1.1 >*/ > public static final int DEACTIVATION_REASON_DISABLED = 1; > /** >* The component instance was deactivated because a > reference became unsatisfied. >* >* @since 1.1 >*/ > public static final int DEACTIVATION_REASON_REFERENCE = 2; > /** >* The component instance was deactivated because its > configuration was changed. >* >* @since 1.1 >*/ > public static final int > DEACTIVATION_REASON_CONFIGURATION_MODIFIED = 3; > /** >* The component instance was deactivated because its > configuration was deleted. >* >* @since 1.1 >*/ > public static final int > DEACTIVATION_REASON_CONFIGURATION_DELETED = 4; > /** >* The component instance was deactivated because the > component was disposed. >* >* @since 1.1 >*/ > public static final int DEACTIVATION_REASON_DISPOSED = 5; > /** >* The component instance was deactivated because the > bundle was stopped. >* >* @since 1.1 >
[jira] Updated: (FELIX-930) XML schema namespace change
[ https://issues.apache.org/jira/browse/FELIX-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-930: Assignee: Felix Meschberger > XML schema namespace change > --- > > Key: FELIX-930 > URL: https://issues.apache.org/jira/browse/FELIX-930 > Project: Felix > Issue Type: New Feature > Components: Declarative Services (SCR) >Affects Versions: scr-1.0.6 > Environment: OSGi RFC-0134, OSGi R4.2 Early Draft 2 > (http://www.osgi.org/download/osgi-4.2-early-draft2.pdf) >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: scr-1.2.0 > > > The schema has been updated and thus has a new namespace is updated to > http://www.osgi.org/xmlns/scr/v1.1.0 > This is due to changes to support backwards and forwards computability in the > future (after this namespace change). Hopefully we can avoid further > namespace changes by introducing extra requirements on the SCR parser at this > time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-924) No component instance if no Configuration
[ https://issues.apache.org/jira/browse/FELIX-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-924: Assignee: Felix Meschberger > No component instance if no Configuration > - > > Key: FELIX-924 > URL: https://issues.apache.org/jira/browse/FELIX-924 > Project: Felix > Issue Type: New Feature > Components: Declarative Services (SCR) >Affects Versions: scr-1.0.6 > Environment: OSGi RFC-0134, OSGi R4.2 Early Draft 2 > (http://www.osgi.org/download/osgi-4.2-early-draft2.pdf) >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: scr-1.2.0 > > > A way is needed for the component declaration to say only create a component > configuration IF there is a Configuration( or Configurations). > To support this, the follow attribute is added to the component element: > default="optional" use="optional" /> > > > > > > > > If the attribute is present and set to require, then a component cannot be > satisfied (section 112.5.2) unless there is a Configuration in > ConfigurationAdmin for the component. In this situation, the No Configuration > case in 112.7 does not apply.If the component is a Factory Component and the > component is not satisfied because there is no Configuration present, then > the ComponentFactory service will not be registered. > If the attribute is present and set to ignore, then ConfigurationAdmin will > not be consulted for the component. In this situation, only the No > Configuration case in 112.7 applies. > If the attribute is not present or present and set to optional, then SCR will > act as it did prior to this RFC. That is, a Configuration will be used if > present in ConfigurationAdmin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-929) Making name attributes optional
[ https://issues.apache.org/jira/browse/FELIX-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-929: Assignee: Felix Meschberger > Making name attributes optional > --- > > Key: FELIX-929 > URL: https://issues.apache.org/jira/browse/FELIX-929 > Project: Felix > Issue Type: New Feature > Components: Declarative Services (SCR) >Affects Versions: scr-1.0.6 > Environment: OSGi RFC-0134, OSGi R4.2 Early Draft 2 > (http://www.osgi.org/download/osgi-4.2-early-draft2.pdf) >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: scr-1.2.0 > > > To reduce the amount of XML that must be written for a component description, > the name attributes of the component and reference elements will be changed > from required to optional. This change is only effective for documents in the > new namespace. > The default value of the name attribute of the component element is the value > of the class attribute of the nested implementation element. > The default value of the name attribute of the reference element is the value > of the interface attribute of the reference element. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Release Status of Deployment Admin Implementation
Hi, just found that the deployment admin implementation (currently version 0.9.0-SNAPSHOT) has not ever been released under the apache flag. Any plans to do so ? I see just http://issues.apache.org/jira/browse/FELIX-454: Autoconf http://issues.apache.org/jira/browse/FELIX-518: Localization Will the release delayed until both "features" are solved ? Otherwise i would like to see this - formally donated as 1.0 - version soon as 0.9.0 or so (current snapshot). Also, since recently it depends on a not yet released dependencymanager version (2.0.2-SNAPSHOT). There is "just" an outstanding patch: http://issues.apache.org/jira/browse/FELIX-1201 Probably start with this ? Toni -- Toni Menzel Independent Software Developer Professional Profile: http://okidokiteam.com t...@okidokiteam.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software.
