On 11/21/06, Don Brown <[EMAIL PROTECTED]> wrote:
Ah, OK, I see where you are coming from now. Sure, if you use the
classpath provider, the problem is really solved. We could create a
mapper for every action method we discover - "action", "action!execute",
"action!input" - which also has the advantage of making the
configuration browser plugin, which I think we really should promote
more, more useful.
Speaking of ClasspathConfigurationProvider, what is the use case for
this swatch from processActionClass:
if (actionName.length() > 1) {
int lowerPos = actionName.lastIndexOf('/') + 1;
StringBuilder sb = new StringBuilder();
sb.append(actionName.substring(0, lowerPos));
sb.append(Character.toLowerCase(actionName.charAt(lowerPos)));
sb.append(actionName.substring(lowerPos + 1));
actionName = sb.toString();
}
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
