Brockman Bulger wrote:
Correct.Using Rickard's approach has another benefit:<actions> <package prefixes="webwork.action.standard"> <action name="Redirect" alias="redirect"/> </package>
Since the fully qualified classname of the action can be determined at startup, the PrefixActionFactoryProxy wouldn't have to try each package prefix to determine the classname at runtime. In other words, we could basically remove the PrefixActionFactoryProxy class and shorten the factory stack. Unless I missed something.
And this is the main reason I just fixed my AOP framework configuration to have this. I used to have a prefix list of about 10-15 packages, and the config phase was just dead slow due to all the ClassNotFoundExceptions. Using this <package> strategy to minimize the classloading misses speeds things up A LOT.
/Rickard
--
Rickard Öberg
[EMAIL PROTECTED]
Senselogic
Got blog? I do. http://dreambean.com
-------------------------------------------------------
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
