I believe we should think about this from the perspective of the ruby script that would eventually call against the interface. It would be extremely unusual for a ruby script to be calling initialize directly, under any circumstances. Because it's typically protected, it's simply not done. By that logic, I think we should not allow initialize to propagate from the Java interface to the callable set of methods on the proxied Ruby object. I don't think it would feel right (and it would complicate the process of defining proxies' initialize methods across the board).
So then we need a way to map the Java interface's "initialize" to something callable in Ruby. I don't have any good ideas for this one yet.
On 5/14/06,
David Corbin <[EMAIL PROTECTED]> wrote:
I ran across a problem today. I was implementing a Java interface in Ruby.
The interface had an method "initialize(...)" defined in it. This creates a
quandry, of course, because the initialize method is used during
construction.
I'm not sure what the right solution for JRuby is. Ideas?
I suspect you could write a ruby implementation that implmented initialize
"smartly enough" to double as a ruby initialize, and as the interface
implementation but you shouldn't have to.
David
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Jruby-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jruby-devel
--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com
