Java 2
Status
JBootstrap
JDK 1.2
JDK 1.3
JDK 1.4
JDK 1.5
JDK 1.6

JDK 1.2.2 FAQ

  1. Whats the best place to ask questions about the FreeBSD JDK 1.2.2?

    Please first look at some of the online documentation, such as Kees Jan Koster's web site regarding JDK 1.2.2 on FreeBSD which is found at http://www.kjkoster.org/java/. Some other possibilities are the official FreeBSD Java porting pages and some information in the Blackdown Linux JDK FAQ may also be helpful (this can be found at http://www.blackdown.org/java-linux/docs/support/faq-release/). If you can't find your answer anywhere there or in the official Java documentation at http://java.sun.com/ then the best option is to ask on the FreeBSD Java mailing list. Information about subscribing to it, and other FreeBSD mailing lists, can be found at http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL.

  2. Why do I always get the warning "Font specified in font.properties not found [-*-zapf dingbats-medium-r-normal-*-*-%d-*-*-p-*-adobe-fontspecific]"

    This particular font is part of the URW font package. Information on retrieving and installing these fonts is available from the Gimp font page at http://www.gimp.org/fonts.html. You can read more about this font at http://www.blackdown.org/java-linux/docs/support/faq-release/FAQ-java-linux-6.html#ss6.4 under the question "Will the situation with TrueType fonts get better?".

  3. Why is there an extra font.properties included with the patchset?

    This font.properties was contributed by Robert Swindells and uses the URW fonts entirely (the default font.properties predominantly uses the TrueType fonts included with the JDK source code, save for the exception mentioned in 2.). Most people find that using this font.properties produces much better looking fonts than the default font.properties. It isn't the default font.properties because TrueType fonts are necessary for Java2D (again, check out the Blackdown FAQ on fonts at http://www.blackdown.org/java-linux/docs/support/faq-release/FAQ-java-linux-6.html#ss6.4 this time under the question "Why are TrueType fonts required for Java 2?"

    See the note in 2. about obtaining URW fonts if you want to use the extra font.properties file.

  4. Why can't I use DGS as a replacement for the DPS library the JDK wants to link against?

    From a standpoint of functionality, you can, and it works quite well. The issue is that portions of DGS are under the GPL, which is incompatible with the SCSL that you agreed to to get the JDK source code (see http://www.gnu.org/philosophy/license-list.html). So, using DGS in this way may be a violation of the GPL. I have received some opinions that as we are only using the dps client libraries and that portion of the code has been done by Adobe that using DGS may be permissible, but I don't feel comfortable with this personally.

    One possible alternative mentioned on the FreeBSD Java mailing list by Taguchi-san is the use of the DPS libraries that come as part of XFree86 4.0. These are certainly under a compatible license. I have had no difficulty compiling a JDK against these libraries, but have not performed any testing yet. People who are using earlier versions of XFree86 should note that the DPS libraries can be installed as part of the XFree86-4-libraries port without moving to XFree86 4.0 completely (just make sure you use a PREFIX other than /usr/X11R6 or you will over write your current XFree86 installation!).

  5. I can't get JBuilder 3.5 to work with JDK 1.2.2 on FreeBSD.

    You need jpda.jar. Rob Furphy writes on the FreeBSD Java mailing list:

    "Place the jpda.jar and dt.jar files from the Linux RC4 distro into the same place in the FreeBSD distro (/lib>) and Jbuilder will work. I am certain jpda.jar is needed, not as sure for dt.jar but it doesn't hurt anything. These files seem like they are part of Java1.3 and Borland/Sun included them in the JBuilder/Sun Java1.2 for JBuilder, (and Blackdown subsequently included them in RC4 - we should probably do the same)."

    [Note, it appears as though only jpda.jar is needed.]

    Note that just installing jpda.jar doesn't provide the full range of JPDA functionality. For full, but experimental, JPDA support please see the FreeBSD JPDA patches which are available at http://www.eyesbeyond.com/freebsddom/java/jpda.html

  6. Should I use OpenMotif or Lesstif?

    I've currently found that I have a few less graphical problems when using OpenMotif, particularly in regards to appletviewer, so I would recommend people currently use that. For instance, on Kees Jan Koster's web page http://www.kjkoster.org/java/ he mentions the problem:

    "Here's a little problem that I noticed by accident. It seems that mouse events are not limited to the menu once it's opened. To reproduce this, start the wire-frame applet. I used applet number two, the dinosaur. Click on the applet's menu, and hold down the mouse. Now drag the mouse down, then off the menu, onto the regular applet canvas. Notice how the dinosaur responds to the mouse dragging events with the menu still open."

    This only occurs for me when I compile the JDK with Lesstif. There are some additional problems which are similarly Lesstif specific.

    Note that this information is for Lesstif 0.90.5 and OpenMotif 2.1.30 build 2. It should be recognised that Lesstif is still under development and in the future may become a comparable or better alternative.

  7. Why isn't there a binary release of the JDK 1.2.2 for FreeBSD?

    There have been some issues which have prevent the FreeBSD Java Porting team from making such a release and I personally cannot make such a release due to the conditions in the SCSL.

    Things are looking up in this regard though, see the announcement at http://www.bsdi.com/news/press/20000607

  8. I have a machine with a limited amount of memory, can I stop the java process taking up so much?

    If you have a limited amount of memory, try setting the environment variable _JVM_LOWMEM, e.g.

    setenv _JVM_LOWMEM yes

    or

    _JVM_LOWMEM=yes; export _JVM_LOWMEM

    (depending on whether you are using sh or csh). This will probably save you in the order of ~50M of memory but may cause problems with large applications.

    For more fine grained control over memory usage I suggest using the java command line memory allocation options such as -Xmx.