Mailing-List: contact syncope-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: syncope-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of mrvanes@gmail.com designates
 209.85.223.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <507ED6FF.2040700@apache.org>
References: 
 <CAFrnU35kGjO-TCWhbv7RqNAu8jx=KyWkFLqb6vmV+Fg3GTFA1A@mail.gmail.com>
	<507BCB81.4020102@apache.org>
	<507ED6FF.2040700@apache.org>
Date: Thu, 18 Oct 2012 08:47:06 +0200
Message-ID: 
 <CAFrnU37C_G5Ds6LwqSGPzfueO3t=FFDX1NQw+5zz_hkJRUJYjA@mail.gmail.com>
Subject: Re: csvdir connector
From: Martin van Es <mrvanes@gmail.com>
To: syncope-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Francesco,

On Wed, Oct 17, 2012 at 6:04 PM, Francesco Chicchiricc=F2
<ilgrosso@apache.org> wrote:
> FYI, CSVDir connector bundle 0.5 (including this fix) was released
> yesterday: I've updated the SNAPSHOT versions to include it.

Thx for the quick fix!

Dropped the csvdir 0.5 jar in my bundles dir and it works. One remark howev=
er:
It's a PITA to deploy this new connector because I can not reassign a
new bundle to an existing connector, nor was I able to assign a
different connector to an existing resource. I even had to reconstruct
my synchronisation task!
I realise this scenario is not likely to happen in production, but I
don't want to think about the complications of un- and re-assigning
10.000+ resources to my population just because a critical bug or
feature xyz was fixed in some back-end driver?! Maybe we could at
least think of a way to allow reassigning connector bundles if only
the minor version was changed or so?

Best regards,
Martin