[
https://issues.apache.org/jira/browse/CLEREZZA-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088128#comment-14088128
]
Minto van der Sluis edited comment on CLEREZZA-939 at 8/6/14 8:11 PM:
----------------------------------------------------------------------
In reply to Reto (see mail thread):
... and the TcManager to be activated only if a component actually requests
it.
Is it possible to only start a service when some other component actually
requires it? If this is possible shouldn't this be the prefered way to access
triple collection as a service as well. Then there is no longer any necessity
to register all triple collections as server beforehand.
was (Author: misl):
In reply to Reto (see mail thread):
... and the TcManager to be activated only if a component actually requests
it.
Is it possible to only start a service when some other component actually
requires it? If this possible shouldn't this be the prefered way to access
triple collection as a service as well. Then there is no longer any necessity
to register all triple collections as server beforehand.
> Create separate service to register the triple Collections as services
> ----------------------------------------------------------------------
>
> Key: CLEREZZA-939
> URL: https://issues.apache.org/jira/browse/CLEREZZA-939
> Project: Clerezza
> Issue Type: Bug
> Reporter: Minto van der Sluis
>
> TcManager has functionality to register every triple collection (graph) as a
> service. As a result bundle startup slows down with a very large number of
> triple collections (graphs).
> Separating this functionality in a separate service reduces TcManager
> complexity. This service should be configurable to be able to disable the
> triple collection name as a service functionality.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
