[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] bundle configuration files as JSON or XML
- From: Ovidiu Deac <ovidiudeac@xxxxxxxxx>
- Date: Thu, 14 Apr 2011 18:14:20 +0300
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=YNc3eZDOHUUwlsr80xKAhg4zEOAPOfW1xAWvNFzAGBcOuModUpmCxyM7yAeSr4G8h9 ftwJSlPIxEUkVjJFk+OaFH2uVbAJRL7oOO6p8L9BmNiEh/lx7PHou0Wf+jjkU0wqNdc1 R5SaUkkq+nDsuoGG5MKuzkb+LAudkmE3fDiS0=
Thanks for replying.
The actual problem is this. We need some complex configuration which
is hard to write in a .properties file so we have two files: one
.properties file which points to an .xml file containing the full
When somebody changes the xml he will also "touch" the properties file
such that the configuration change is loaded by the bundle.
This pretty ugly.
Now I was thinking that it would be nice to have only the .xml file
and be notified by Virgo when the file is changed.
This xml file could have any structure the bundle needs.
On Thu, Apr 14, 2011 at 6:04 PM, Dmitry Sklyut <dmitry@xxxxxxxxxxx> wrote:
> Hi Ovidiu,
> What is the format of XML file are you looking for? XML as in
> java.util.Properities xml format or some custom mechanism?
> If Properties - it will be very simple to do. Virgo just needs a very minor
> code change to support it.
> Otherwise - you are looking at the custom deployment type. This is not
> documented well, but I will be happy to lend a hand if you decide to go down
> that route.
> On Thu, Apr 14, 2011 at 10:50 AM, Ovidiu Deac <ovidiudeac@xxxxxxxxx> wrote:
>> I am familiar with the bundle configuration mechanism but the
>> properties files don't give us enough flexibility so I wonder if it is
>> possible to configure the bundle using an XML file which deployed in
>> the pickup dir.
>> virgo-dev mailing list
> virgo-dev mailing list