Date: Thu, 02 Sep 2004 10:00:27 +0300 From: Ari Suutari <ari@suutari.iki.fi> To: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr> Cc: freebsd-java@freebsd.org Subject: Re: Java Communication API for FreeBSD Input Stream Problem Message-ID: <4136C50B.2050906@suutari.iki.fi> In-Reply-To: <20040901142643.GA80717@arabica.esil.univ-mrs.fr> References: <20040831120745.L66028@hawat.cc.ubbcluj.ro> <20040901072358.GA45042@anyware12.anyware> <20040901142643.GA80717@arabica.esil.univ-mrs.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Herve Quiroz wrote: > Jean-Baptiste, > > On Wed, Sep 01, 2004 at 09:24:01AM +0200, Jean-Baptiste Quenot wrote: > >>You may want to give a try to RXTX, I have ported it to FreeBSD: >> >>http://caraldi.com/jbq/ports/rxtx/ >>http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/65396 >> >>Basically, RXTX is an open-source implementation of Java Comm API, and >>AFAICT it works right out of the box! See contrib/SimpleRead.java in >>the source distribution for a simple example that just works. >> I kind of missed this thread before. However, current rxtx version has problems how it handles the JNI pointer inside it's C code. This might or might not be a showstopper (might crash VM when it hits). The rxtx author is aware of the problem, but I don't know if it has been fixed. I was hoping that I would no longer have to maintain FreeBSD commapi and tried to use RXTX to talk to dallas 1-wire devices (see www.ibutton.com). I was hit by this bug and I decided to continue using FreeBSD commapi since it looked that the fix for rxtx was not coming soon. Ari S.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4136C50B.2050906>