I can attest to the speed assertions too. When Tom demonstrated this for me on Friday I would swear the swing demo ran much faster than before...perhaps as fast as pure Java. Granted, there's very little Ruby code involved, but the Java integration layer is no longer a source of performance issues.
On 3/20/06, Thomas E Enebo <[EMAIL PROTECTED]> wrote:
I committed a fix this morning which fixes this example.
The fix removes lazy evaluation and moves instance method creation
for proxies into Java (from Ruby in javasupport.rb). In fact instance
method calls to java from ruby are now even a bit faster than before..
Let me know if this causes problems. I do not expect any issues
unless java beans introspector comes to a different conclusion than
our by-hand logic we had before (no unit tests regressed) for defining
short-hand bean methods. If we do run into issues with the short
beanname methods, then it is likely better behavior now.
Proxy loading appears to be largely the same speed as with lazy
proxies.
--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com
