From owner-freebsd-java@FreeBSD.ORG Sat Dec 20 11:31:10 2003 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4D2F16A4CE for ; Sat, 20 Dec 2003 11:31:10 -0800 (PST) Received: from mallard.propagation.net (mallard.propagation.net [66.34.7.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFE8D43D54 for ; Sat, 20 Dec 2003 11:30:49 -0800 (PST) (envelope-from evan@eeaston.com) Received: from h1.int.eeaston.com (c-24-245-65-42.mn.client2.attbi.com [24.245.65.42]) by mallard.propagation.net (8.9.3p2/8.8.5) with ESMTP id NAA00110; Sat, 20 Dec 2003 13:13:33 -0600 Received: from eeaston.com (eastonlaptop [192.168.0.90]) by h1.int.eeaston.com (Postfix) with ESMTP id 466AA3999D; Sat, 20 Dec 2003 13:13:17 -0600 (CST) Message-ID: <3FE49F4D.2030309@eeaston.com> Date: Sat, 20 Dec 2003 13:13:17 -0600 From: Evan Easton User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexey Zelkin , freebsd-java@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: jdk1.4.2: plugin & javaws users feedback request X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Dec 2003 19:31:11 -0000 On Monday 08 December 2003 14:32, Alexey Zelkin wrote: > Gentelmen, > > If you are using jdk1.4.2p5 and also use plugin and/or javaws, then > I would ask you send me your feedbacks (positive and/or negative) about > their correctnes and functionality. I am not using them heavily, so > not able to test them a lot. > > Thank you in advance! / /Alexey, I just installed jdk 1.4.2p5 and tried to use javaws on 5.1-CURRENT. I ran into two issues with javaws. (1) when I run javaws nothing appears to happen. Top shows javawsbin spinning it's wheels using ~40% CPU, but other than that there's no outward symptoms it's doing anything useful. I tried setting env var JAVAWS_TRACE_NATIVE=1 , but this did not cause javawsbin to show any more info. I was able to get it to run with the following script: #!/bin/sh JAVA_HOME=/usr/local/jdk1.4.2 JAVAWS_HOME=$JAVA_HOME/jre/javaws java -cp $JAVAWS_HOME/javaws.jar:$JAVAWS_HOME/javaws-l10n.jar \ -Djnlpx.jvm=$JAVA_HOME/jre/bin/java -Djnlpx.home=$JAVAWS_HOME \ -Djnlpx.deployment.system.home=$JAVAWS_HOME \ -Djnlpx.deployment.user.home=/home/evan/.javaws \ -Djnlpx.home=$JAVAWS_HOME \ -Djava.security.policy=$JAVAWS_HOME/javaws.policy \ com.sun.javaws.Main "$@" So it seems something's wrong in javawsbin. I don't know how to provide more useful info to you on this. Give me a hint and I'll try. (2) Using the above script, I'm able to run some java webstart apps. However, because java -version reports '1.4.2-p5', Java Web Start doesn't consider the JRE to be a 1.4.2 **FCS** version and will not treat the current VM as valid if a java webstart app wants to run with Java 1.4. Take a look at the jnlp spec. (http://java.sun.com/j2se/1.4.2/docs/guide/jws/developersguide/syntax.html) . Look for the text following the syntax for the j2se version command element: If a platform version is specified (i.e., no |href| attribute is provided), Java Web Start will not consider an installed non-FCS (i.e., milestone) JRE as a match. E.g., a request of the form would not consider an installed 1.4.1-ea or 1.4.2-beta JRE as a match for the request. Starting with 1.3.0, a JRE from Sun Microsystems, Inc., is by convention a non-FCS (milestone) JRE if there is a dash (|-|) in the version string. So this version of the JDK is unusable for apps that require 1.4 or higher (and possibly ones that require older versions of java too). I tried overriding the version from my script above by adding the following system property overrides, but no luck: | -Djava.version=1.4.2 || -Djava.vm.specification.version=1.4.2| | -Djava.vm.version=1.4.2| | -Djava.specification.version=1.4.2| I haven't tried to rebuild the jdk to report a version of '1.4.2' instead of '1.4.2-p5' but it seems that this needs to be done to make javaws usable. Note that Sun uses a _XX suffix on their patch releases. Perhaps the version reported should be changes to '1.4.2_p5' or to be a little more consisted with Sun, '1.4.2_05'. Evan / /