Currently we "overload" the property name in rhq-plugin.xml to provide the expression to filter down to the augeas node corresponding to the property. Because the property names have limited length (currently 100 chars), that obviously limits us in the complexity of the augeas expressions possible. We should come up with a better way of handling this. The simplest approach would be to modify augeas plugin to use some kind of facade interface to obtain the augeas expression from given property (or property definition) rather than directly using the name of those.
Maybe we should keep using the names as the default impl of this new API, e.g.: AugeasConfigurationComponent: protected String getAugeasNodeExpression(PropertyDefinition propDef) { return propDef.getName(); } CronTabComponent: @Override protected String getAugeasNodeExpression(PropertyDefinition propDef) { return NODE_EXPRESSION_MAP.get(propDef.getName()); } That way we can keep the mapping metadata in the descriptor for the simpler cases.
Yes, I have it already implemented like that. protected String getAugeasPathRelativeToParent(PropertyDefinition propDef, AugeasNode parentNode, Augeas augeas); with the default implementation as you suggested... This is in my local branch, will commit it soonish with the updates to the cron plugin...
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2476
mass add of key word FutureFeature to help track
Lukas, please close if this is done/out of date.
This has been in the code base for some time now.