On 14 Apr 2011, at 16:14, Ovidiu Deac wrote:
> 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
>> 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
>>> 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
> virgo-dev mailing list
virgo-dev mailing list