#175 Dynamic Configuration Mechanism - Diffa

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#175 new

Dynamic Configuration Mechanism

Reported by Ben Hood | February 7th, 2011 @ 12:44 PM

#169 introduced a table for persisting Diffa level properties as simple keys, eliminating the need for property files to specify default values. However, this mechanism needs to be jazzed up a little more so that dependent components can receive values updates without having to restart. So presumably instead of passing in a value of each property to dependent components, you would pass in a pointer. For example, you could read the value out of Hibernate and use the 2-level cache.

No comments found

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.