Agent properties now have aliases. This was originally invented so the Java agent could mimic the properties the C agent uses - thus addressing a criticism that the Java and C agents use different properties to do the same thing. I've taken advantage of this feature to clean up some of the older property names, replacing them with new, more meaningful names.
The new names have some consistency (enabling/disabling properties end with .enabled, map properties end with .map and list properties end with .list, etc. etc.).
This strategy creates an obvious problem. If the two properties are defined by the user:
which of the two property assignments "wins"? Currently it is completely random (dictated by the EntrySet for the map the properties are stored in). In order to preserve backward compatibility, I propose an alphabetical sort which would produce the following order:
This guarantees that the old style properties com.sun.identify.agents.config.* (which will continue to be supported by the XUI for the immediate future) will override the values of any other properties defined within the agent.