|
Re: Apache Batik: msg#00009lang.jruby.user
Tim does make a good point...include_class has lately become a preferred method of "importing" Java classes into Ruby, because it not only has less overhead than include_package, but it allows you to explicitly see and name the incoming classes. - Charlie On 2/7/06, tim@xxxxxxxxxxxxx <tim@xxxxxxxxxxxxx> wrote: > > PS I'm not an expert on JRuby or Java integration BTW but I have used it, but > I've used the other model described on > http://jruby.sourceforge.net/docs/java-overview.shtml > > require 'java' > > include_class 'java.util.Random' > r = Random.new > puts r.nextInt > > > Have you tried doing it this way instead? > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Apache Batik: 00009, tim |
|---|---|
| Next by Date: | Re: Apache Batik: 00009, Thomas E Enebo |
| Previous by Thread: | Re: Apache Batiki: 00009, tim |
| Next by Thread: | RE: Apache Batik: 00009, Yemi D. Bedu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |