Howdy,
I am looking for some feedback on the attached classes I wrote to do ${...} style parameter substitution. Please let me know if this whole thing is silly:
Josh,
Looks interesting! I didn't review the code completely, but from first blush (just from the size of the code), it doesn't look like you handle multiple ".", e.g., "mail.myattribute.customproperty". Also, I'm not sure how you're handle type coercion/primitives or if that's something you think needs addressing.
I would think relying on Jelly or EL or something like that might be a nice way to handle many of those issues without having to duplicate effort or retrain people as the parameter passing feature gets more complex.
It is nice how you suggest offering it optionally. There has been talk about doing something like this for the matcher argument themselves or tying it into the spool processing, but those get more complicated.
Anyway, just some initial feedback. Hope it helps.
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
