Well, we're backed to where I'd gotten to before, which is going to take some
time to narrow down. I'm getting an "not found exception" out of some of our
java code, that I'm not getting with 0.8.2.
David
On Monday 20 March 2006 21:09, Thomas E Enebo wrote:
> Fixed. At least this case is. I
That works well where I had spotted the breakage. I'm now check our other bits
and parts.
On Monday 20 March 2006 21:09, Thomas E Enebo wrote:
> Fixed. At least this case is. I was not overriding any Ruby functions
> which already existed. 'print' was one of those. I removed this
> restric
Fixed. At least this case is. I was not overriding any Ruby functions
which already existed. 'print' was one of those. I removed this
restriction with exception of 'class', which java support reqiures.
I suspect there is more and will continue looking, but I wanted to
give you something to w
Who new it would be so simple :)
On Monday 20 March 2006 09:00 pm, Thomas E Enebo wrote:
> I am on it:
>
> require 'java'
>
> include_class 'java.io.PrintWriter'
> include_class 'java.lang.System'
>
> p = PrintWriter.new(System.out)
> p.print "HEH"
> p.close
>
> On Mon, 20 Mar 2006, David Corbin
I am on it:
require 'java'
include_class 'java.io.PrintWriter'
include_class 'java.lang.System'
p = PrintWriter.new(System.out)
p.print "HEH"
p.close
On Mon, 20 Mar 2006, David Corbin defenestrated me:
> On Monday 20 March 2006 10:22 am, Thomas E Enebo wrote:
> > I committed a fix this mornin
On Mon, 20 Mar 2006, David Corbin defenestrated me:
> On Monday 20 March 2006 10:22 am, Thomas E Enebo 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.
On Monday 20 March 2006 10:22 am, Thomas E Enebo 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
I concur with adopting Java's built-in bean attribute mapping logic as written. There should be very few cases where we want to venture outside this standard, and deferring to Java means we have less code to support.
I can attest to the speed assertions too. When Tom demonstrated this for me on Fri
