May be don't use reflection then and delegate this to the action itself. For e.g, this can be implemented by adding an init method to the Action interface that take a map as parameter. This would also allow us to differentiate between init parameter ( usually for configuration purpose ) and runtime parameter ( usually use input ).
Regards, Low --- Rickard_Öberg <[EMAIL PROTECTED]> wrote: > Jason Carreira wrote: > > Couldn't the Method objects found the first time through reflection for > > parameterizing the Action instances be cached and reused, making the > > reflection performance hit negligible? I've never profiled reflection to > > see where the biggest performance hit is, but if it's the Class and > > Method lookup, this could help (and be used for the Action field > > population, as well) > > The biggest hit is in lookup, absolutely. However, there's overhead for > type conversion too. > > And if you compare it with a simple Conf.getValue() call the overhead is > MUCH higher. > > /Rickard > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
