Hi Tom, This would certainly not be a feature but a bug. But since Configuration.update immediately stores a configuration object, such that persistene and internal cache have the same state, this is unexpected.
Can you provide me with a short test case to reproduce the issue ? Thank you very much. Regards Felix On 6/29/07, Tom Remoleur <[EMAIL PROTECTED]> wrote:
Hi all, I've got a problem with the Felix configuration admin service : For accessing to configuration I'm both using the configuration admin "getConfiguration" and "listConfiguration" methods, but if I update a configuration using first the "listConfiguration" method and after I access to the same conf using the "getConfiguration" method, it's return me the old configuration without the previous update modifications. I've debugged my application and I've noticed the "listConfiguration" command read the configuration from the persistant store by the "getConfiguration" retrieve them from a cache but when a configuration getted by "listConfiguration" is updated the cached configuration isn't updated. Is it a feature or a bug ? Thanks Tom Remoleur --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
