https://issues.apache.org/bugzilla/show_bug.cgi?id=55882
--- Comment #4 from Andreas Beeker <[email protected]> --- To solve this, there are two ways: - either we introduce some kind of hash map caching of the underlying properties, and have to make sure that the map is synced when somebody changes something underneath - or you call the getUnderlyingProperties() method and fill the underlying properties yourself Although always iterating over props.getProperties().getPropertyList() is probably the reason for that bad performance, I'm a bit reluctant to implement a caching method here, as the second method is probably sufficient for your case and I don't need to worry about syncing. Please correct me, if I'm totally wrong, but I think, that these many properties aren't usual and to move the logic into users code is ok. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
