Since Struts already depends on jakarta-oro, is there a reason not to use it for doing pattern-based mapping, rather than the home-grown methodology that's in the current builds?
I don't have a use case for it yet, but since I was a perl hacker before I came to Java, I speak regex reasonably fluently, so it seems to me more useful to have the full power of regular expressions available.
I have a few questions about simulating the ~= operation in ORO and Javascript for the validator code,
but I'll save those for later.
If there are strong feelings in favor of the status quo, I think it would be easy enough to make "matcherClassName" a property of ModuleConfigImpl and support pluggable matchers.
I guess technically, only Validator depends on jakarta-oro; I might be persuaded that that's a reason to keep from adding it to the core, maybe...
I doubt anyone could object on the basis of performance, unless they create a benchmark to support the claim it's much slower.
Anywhere we can simplify the logic and eliminate duplication is a good thing.
Joe
Rob
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
