OK, I was playing with Ognl today and performance became a problem. Below is my post to ognl-interest, I'll keep everyone posted. In the meantime, maybe ditching PropertyEditors but coming up with our own (FAST) BeanUtil implementation that doesn't use PropertyEditors would be best. It shouldn't need to be very complex. The main things we need are:
- complete data conversion for both setting and getting data - ability to write our own data converters for each webwork action (not class) ------------- Uh oh... I may have hit a major roadblock in trying to switch to using Ognl in WebWork: it appears to be VERY slow. I ran a simple test, setting 7 different attribute types (some of which involve type conversion), repeating 1000 times: Total time (OGNL): 2463ms Total time (BeanUtil): 91ms BeanUtil is a WebWork utility method that uses the JavaBeans APIs (PropertyEditor, etc). Any thoughts on this? I'm using the optimized binary under JDK 1.4.1. ------------ ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
