[
https://issues.apache.org/jira/browse/SLING-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216006#comment-14216006
]
Carsten Ziegeler commented on SLING-4154:
-----------------------------------------
[~mpetria] If I understand that proposal we're back to a situation were we have
duplicate information, resources creating OSGi configurations. Which can turn
into a nightmare and might get out of sync. I think it would really help to
build up the design based on the fact that we have OSGi services configured
through OSGi configurations, so we start bottom-up instead of a mixture of
top-down/bottom-up. However for this, we really need hard requirements and use
cases.
We have run modes, which would be one way of dealing with configurations for
other environments; services in OSGi can be lazy which means if they are not
used, they are not active. This would solve "zombie services" as well. And I
guess there are more ways to solve this in a clean way.
> Discuss distribution components creation and configuration
> -----------------------------------------------------------
>
> Key: SLING-4154
> URL: https://issues.apache.org/jira/browse/SLING-4154
> Project: Sling
> Issue Type: Task
> Components: Distribution
> Reporter: Marius Petria
> Fix For: Content Distribution 0.2.0
>
>
> Distribution has one main component (agent) and several secondary components
> (triggers, exporters and importers).
> These can be created as java objects using a DistributionComponentFactory.
> The core framework provides a DefaultDistributionComponentFactory that will
> create the components implemented in the core but a client can define its own
> components and factory and the default component factory will use those to
> create a component it does not know of.
> The core framework also provides two ways of registering such a java object
> as an OSGI service:
> 1. using osgi configs, the osgi properties are parsed and passed to the
> factory, a component is created and registered
> (GenericDistributionComponentFactory)
> 2. resource configs, the properties of a resource are parsed and passed to
> the factory, a component is created and registered
> (ResourceBasedDistributionComponentFactory)
> Components registered as OSGI services are available as resources via
> OsgiServicePropertiesResourceProvider.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
