Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (athena.apache.org: domain of dariusz.luksza@gmail.com
 designates 209.85.219.225 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type
         :content-transfer-encoding;
        b=Ib2DNizXNdWp74pz67HjVKgBcouM2mR5u5tivOpZeep3Y7X9bcJwVqURER1kw/QDZL
         Fx/7npMmESQZr7oQbGAmQNXavWVuThRRiGDCXvgj8GqLLNGlkGsSMCpo2NDi3wikeefs
         9Y/ZeynSq+2fjHfnePjE9nhq6uV2TYd1SqczY=
MIME-Version: 1.0
From: =?UTF-8?Q?Dariusz_=C5=81uksza?= <dariusz.luksza@gmail.com>
Date: Sat, 25 Apr 2009 19:52:17 +0200
Message-ID: <a224cb0f0904251052tc2551f5rd06f0048ec09c798@mail.gmail.com>
Subject: [c3-monitoring] Logging reconfiguration.
To: dev@cocoon.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi all,

I'm actually starting work on my GSoC project so in near feature you
will be getting a lot of spam from me and Jira ;)

First goal that I want to achieve is logging reconfiguration (I'm sure
that you all ready notice corresponding with it mail from Jira).

I've all read attach small patch to jira issue that adds
cocoon-monitoring module but I have also one question connected with
this patch.

I'm not quite sure what should I do witch "old"
cocoon-configuration-api and cocoon-spring-configurator. Should I :
 [1] add dependency to cocoon-monitoring on cocoon-configuration-api
or cocoon-spring-configurator,
 [2] create another solution based on cocoon-spring-configurator
 [3] integrate both project and add it to c3
?

I've  notice that now in c3 there no division between api and it's
implementation, so I think that first approach wouldn't be good. IMHO
the best solution would be implementing logging reconfiguration from
scratch based on code from cocoon-spring-configurator.

I'm looking froward for yours advices and opinions ;)
-- 
Best regards

Blog: http://luksza.org
LinkedIn: http://www.linkedin.com/in/dariuszluksza