Return-Path: X-Original-To: apmail-manifoldcf-dev-archive@www.apache.org Delivered-To: apmail-manifoldcf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 93B8611B7D for ; Wed, 2 Jul 2014 11:23:59 +0000 (UTC) Received: (qmail 64503 invoked by uid 500); 2 Jul 2014 11:23:53 -0000 Delivered-To: apmail-manifoldcf-dev-archive@manifoldcf.apache.org Received: (qmail 64453 invoked by uid 500); 2 Jul 2014 11:23:53 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 64440 invoked by uid 99); 2 Jul 2014 11:23:53 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jul 2014 11:23:53 +0000 Received: from localhost (HELO MacBook-Pro-de-Rafa.local) (127.0.0.1) (smtp-auth username rharo, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jul 2014 11:23:52 +0000 Message-ID: <53B3EBC6.3030606@apache.org> Date: Wed, 02 Jul 2014 13:23:50 +0200 From: Rafa Haro User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: dev@manifoldcf.apache.org Subject: Re: Configuration Management at Transformation Connectors References: <53B2EA33.4010202@apache.org> <53B3C00D.4090409@apache.org> <53B3DE8E.5090908@apache.org> <53B3E294.8040907@apache.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Karl, El 02/07/14 13:17, Karl Wright escribió: > Hi Rafa, > > Without a concrete example, you won't get a concrete recommendation. But > in general please understand that the architecture is what it is, for very > good reasons, and if you want your connector to work within it, you need to > play by the rules. Of course, I just wanted to be sure about the options. I appreciate a lot you help and your clarifications and I hope that also the uses cases of the developers integrating ManifoldCF can help the community to improve it by addressing (or not :->) the proposed issues. From my side, I'm going to further investigate how the framework works at code level to see if I can extend the Transformation connector workflow for allowing resources initialization from Connectors Configuration and Output Specificiation. Thanks, Rafa > > Thanks, > Karl > > > > On Wed, Jul 2, 2014 at 6:44 AM, Rafa Haro wrote: > >> Hi Karl, >> >> El 02/07/14 12:37, Karl Wright escribió: >> >>> Hi Rafa, >>> >>> If there are a limited number of read-only models, then you can build a >>> static hashmap between model data and the file name, and populate that on >>> demand. >>> >> It is a possibility, although the models stuff was just an example. The >> generic question is how to reuse resources in a Transformation Connector? >> or, which is the proper place in the implementation to initialize a >> resource that has to be reused during a job running? >> >> I'm still missing this because I still don't know where to access the >> Specification object apart from the getPipelineDescription method. So, if >> there is no other point in the architecture, I'm afraid I have to check if >> the initialization has been done or not and even synchronize it by myself. >> >> Thanks for your help so far Karl >> >>