I'll get some demo implementations of JBeans in the sandbox/xwork module and
post my results.
-Pat
- Original Message -
From: Jason Carreira [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, November 01, 2002 4:59 AM
Subject: RE: [OS-webwork] Ognl status
We should also check out http://jbeans.org/ for this stuff... It looks
pretty cool.
-Original Message-
From: Patrick Lightbody [mailto:plightbo;cisco.com]
Sent: Thursday, October 31, 2002 1:53 PM
To: [EMAIL PROTECTED]
Cc: Drew Davidson
Subject: Re: [OS-webwork] Ognl status
Followup:
Drew Davidson pointed out that precompiling the parse trees would speed
things up a TON, which it did:
Total time (OGNL): 2213
Total time (OGNL compiled): 100
Total time (WebWork BeanUtil): 80
Total time (Commons-BeanUtils): 111
You can run these tests yourself by checking out sandbox and running
ant from within the xwork directory. Ognl will allow us to write
TypeConverters for each bean and/or property, but it doesn't have a way
to convert data back to a desired form (String in our case, but since
this is XWork, we'll want to support any type of conversion).
-Pat
- Original Message -
From: Patrick Lightbody [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 30, 2002 4:44 PM
Subject: [OS-webwork] Ognl status
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
---
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
---
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
---
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
