Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Sep 2005 00:35:21 +0300
From:      Panagiotis Astithas <past@ebs.gr>
To:        Panagiotis Astithas <past@ebs.gr>
Cc:        "Georg-W. Koltermann" <gwk@rahn-koltermann.de>, freebsd-java@freebsd.org
Subject:   Re: cant get javaws to start up with jdk1.5p2, also plugin problems
Message-ID:  <43386999.2090906@ebs.gr>
In-Reply-To: <4337A6AF.5000602@ebs.gr>
References:  <1127504815.1265.28.camel@localhost.eu.mscsoftware.com>	<20050923213831.GA14819@misty.eyesbeyond.com> <4337A6AF.5000602@ebs.gr>

next in thread | previous in thread | raw e-mail | index | archive | help
Panagiotis Astithas wrote:
> Greg Lewis wrote:
> 
>> On Fri, Sep 23, 2005 at 09:46:55PM +0200, Georg-W. Koltermann wrote:
>>
>>> from a freshly installed jdk1.5p2 as of today on FreeBSD 5.4 I get:
>>>
>>>        hunter[12]$ echo $JAVA_HOME
>>>        /usr/local/jdk1.5.0
>>>        hunter[13]$ $JAVA_HOME/jre/bin/javaws
>>>        Java Web Start splash screen process exiting ...
>>>        Bad installation. No JRE found in configuration file: Illegal 
>>> byte sequence
>>>        hunter[14]$
>>>
>>> Any idea on how to proceed?
>>
>>
>>
>> So here is the problem with Java Web Start.  Basically I don't know how
>> to use it, so it gets next to no testing unless someone else tests it.
>> I'd greatly appreciate it if someone could point me at some documentation
>> or, even better, give me some examples I could test it with.  All I did
>> for it was forward port the patches from 1.4.2 and made it compile.  I
>> assumed that made it work since as I mentioned above I don't know how to
>> test it.
> 
> 
> 
> You could check out the following links:
> 
> http://java.sun.com/j2se/1.5.0/docs/guide/javaws/index.html
> 
> http://java.sun.com/j2se/1.5.0/docs/guide/javaws/developersguide/javaws.html 
> 
> 
> http://java.sun.com/j2se/1.5.0/docs/guide/javaws/developersguide/contents.html 
> 
> 
> There are some demos here:
> 
> http://java.sun.com/products/javawebstart/demos.html
> 
> 
> I've been meaning to look into this, but haven't found the time yet...

It all boils down to a corrupt deployment.properties file under 
~/.java/deployment/. I'm not sure yet how this file gets like that.

Panagiotis



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43386999.2090906>