From dev-return-5109-archive-asf-public=cust-asf.ponee.io@any23.apache.org Thu Feb 8 22:39:00 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 7BEBD18064F for ; Thu, 8 Feb 2018 22:39:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6B2FE160C4A; Thu, 8 Feb 2018 21:39:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A8235160C34 for ; Thu, 8 Feb 2018 22:38:59 +0100 (CET) Received: (qmail 64327 invoked by uid 500); 8 Feb 2018 21:38:58 -0000 Mailing-List: contact dev-help@any23.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@any23.apache.org Delivered-To: mailing list dev@any23.apache.org Received: (qmail 64312 invoked by uid 99); 8 Feb 2018 21:38:58 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Feb 2018 21:38:58 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 23D85DFBBB; Thu, 8 Feb 2018 21:38:58 +0000 (UTC) From: ansell To: dev@any23.apache.org Reply-To: dev@any23.apache.org References: In-Reply-To: Subject: [GitHub] any23 issue #56: ANY23-321 Add openie toggle functionality to service Content-Type: text/plain Message-Id: <20180208213858.23D85DFBBB@git1-us-west.apache.org> Date: Thu, 8 Feb 2018 21:38:58 +0000 (UTC) Github user ansell commented on the issue: https://github.com/apache/any23/pull/56 I don't have time right now to debug this or work on its design. It isn't a pattern I have worked on in the past. All ``ServiceLoader`` projects that I have worked on in the past either have all of the service Factory objects initialised as startup, or they do periodic scans, but always create and initialise the service Factory objects whenever they are discovered. Is this issue attempting to delay/extract the OpenIE initialisation by delaying/postponing the Factory initialisation? If so, the focus could possibly be on making the OpenIE initialisation lazy to only occur when the Factory is actually required/used to create an object instance. A more configurable lifecycle possibly requires OSGi, which I again have absolutely no experience with, but from the little understanding each time I look, it appears to allow user driven initialisation (push rather than pull, if that makes sense). ---