This repository has been archived by the owner on May 17, 2021. It is now read-only.
change binding project structure to DS 1.2.0 #2027
Comments
tdiekmann
pushed a commit
to tdiekmann/openhab
that referenced
this issue
Jan 23, 2015
…he binding configuration Signed-off-by: Tim Diekmann <tdiekman@tibco.com>
teichsta
added a commit
that referenced
this issue
Jan 25, 2015
changed the archetype default binding project according to #2720
juri8
pushed a commit
to juri8/openhab
that referenced
this issue
Jan 27, 2015
…he binding configuration Signed-off-by: Tim Diekmann <tdiekman@tibco.com>
cdjackson
added a commit
to cdjackson/openhab1-addons
that referenced
this issue
Jan 28, 2015
* master: Bugfix for issue openhab#1351 Configurable command interval Removed annoying bin folders including .project files issue openhab#2027 - added modified callback for dynamic changes to the binding configuration Fix RRD4J error at midnight changed the archetype default binding project according to openhab#2720 updated the copyright header with the year 2015 added immediate="true" flag to binding.xml, otherwise the binding does not get started automatically removed unnecessary imports removed the Activator. The bundleContext is available from the call to the activate method. The static Activator access is discouraged, since it is only valid when the bundle is ACTIVE, however, any code could access the static variable at any point in time Adds the leviton vrcz4-m0z to the zwave database
cdjackson
added a commit
to cdjackson/openhab1-addons
that referenced
this issue
Jan 28, 2015
* zwave-database_updates: Add TKB TZ06 Update codes for Fibaro universal sensor Bugfix for issue openhab#1351 Configurable command interval Removed annoying bin folders including .project files issue openhab#2027 - added modified callback for dynamic changes to the binding configuration Fix RRD4J error at midnight changed the archetype default binding project according to openhab#2720 updated the copyright header with the year 2015 added immediate="true" flag to binding.xml, otherwise the binding does not get started automatically removed unnecessary imports removed the Activator. The bundleContext is available from the call to the activate method. The static Activator access is discouraged, since it is only valid when the bundle is ACTIVE, however, any code could access the static variable at any point in time
cdjackson
added a commit
to cdjackson/openhab1-addons
that referenced
this issue
Jan 28, 2015
* zwave-initialisation: Bugfix for issue openhab#1351 Configurable command interval Removed annoying bin folders including .project files issue openhab#2027 - added modified callback for dynamic changes to the binding configuration Fix RRD4J error at midnight changed the archetype default binding project according to openhab#2720 updated the copyright header with the year 2015 added immediate="true" flag to binding.xml, otherwise the binding does not get started automatically removed unnecessary imports removed the Activator. The bundleContext is available from the call to the activate method. The static Activator access is discouraged, since it is only valid when the bundle is ACTIVE, however, any code could access the static variable at any point in time
|
@tdiekmann, can this issue be closed? |
|
Yes, sure.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Refactor the sample structure of a binding project to use the DS 1.2.0 schema and use the CAS policy required for the DS component.
Eliminate the implementation of the ManagedService and the updated method. Change the signature of the activate() method to take the BundleContext and a Map of configuration objects.
This refactoring simplifies the work for new bindings. The SCR (Service Component Runtime == DS) will activate a component only if there is a configuration available under the configured configuration-pid. Otherwise, the component will not be activated. This removes the complicated code dealing with timing issues around activation and configuration of a binding.
The text was updated successfully, but these errors were encountered: