From: Jost B. <jos...@ya...> - 2005-07-07 16:40:06
|
Hi, > was able > to compile version 2.0.7pre2 against Apples Java 1.5.0_02-36 on Tiger that's great! The C code will not be changed any further, so I expect that the future versions of the bridge will continue to run, even though we don't have the chance to test on MacOS X. > I did not succeed at getting it running using the (named?) sockets OSX should have "unix domain sockets" too, but I guess the problem is JNI related. Apple has changed JNI in an incompatible way; there was a discussion on the gnu java mailing list about this issue. If you compile with make "CFLAG=-DCFG_JAVA_SOCKET_INET" the bridge will use TCP sockets instead even if the configure script reports that "unix domain sockets" are available. This flag is necessary on BSD, too, as BSD usually runs the linux JDK which cannot load the natcJavaBridge.so files that BSD creates. One problem with TCP sockets is that most java implementations create a socket which binds itself to *all* available network interfaces. This might become a security issue if the backend runs on the web-server. We should change this, a LOCAL: backend should bind itself to the local interface only. Regards, Jost Boekemeier --------------------------------- Gesendet von Yahoo! Mail - Jetzt mit 1GB kostenlosem Speicher |