[ 
https://issues.apache.org/jira/browse/SLING-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217764#comment-14217764
 ] 

Marius Petria commented on SLING-4154:
--------------------------------------

[~cziegeler], [~fmeschbe], thanks for the (offline) discussion on how component 
wiring should be done.

We agreed on several things:
1. doing the wiring using standard OSGI config constructs
i.e. have an INTERNAL API for translating json settings into a set of OSGI 
configs  
boolean createComponent(type, properties) 
Map<String,Object> getComponentSettings(type, name)
boolean deleteComponent(type, name)
boolean updateComponent(type, name, properties)

2. Interact with this API first via JCR settings (this is not decided yet to be 
the preferred way)
3. Discuss which way is the best to interact with this API, jcr events, 
resource provider, servlets


> 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)

Reply via email to