From owner-freebsd-java Fri Jun 29 14: 0:33 2001 Delivered-To: freebsd-java@freebsd.org Received: from ns.prologic.com (ns.prologic.com [209.181.124.2]) by hub.freebsd.org (Postfix) with ESMTP id B64D437B407 for ; Fri, 29 Jun 2001 14:00:21 -0700 (PDT) (envelope-from bodkins@prologic.com) Received: from bodkins (ras-2.prologic.com [209.181.124.14]) by ns.prologic.com (8.9.2/8.9.2) with SMTP id NAA54352 for ; Fri, 29 Jun 2001 13:59:58 -0700 (MST) (envelope-from bodkins@prologic.com) Message-ID: <001a01c100de$ffbd72b0$251cd3d0@bodkins> From: "Jim Bodkins (Prologic)" To: Subject: Java and why I have trouble sleeping. Date: Fri, 29 Jun 2001 14:03:49 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0017_01C100A4.51EB3490" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0017_01C100A4.51EB3490 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Jesse Noller - The problem that I had with JRun was the depricated = version of tar that was used to build elements of the .sh not JRun = itself. I have never managed to untar the thing. I did install an "old" = version of tar and even that didnt work. So whether JRun works or not, I = have no idea. Dead end right now. I tried posting in general JRun = questions on the allaire forum (that cold fusion thingy) but didnt get = very far. Gabor Kinces - Thanks for the info. I'll bet you are right about the = Hot Spot VM and threads. I tried posting to the Enhydra lists, but was = blocked "for review" or something by a moderator. Not much help there = actually. Ernst de Haan - A port should be easy, but this is so far an = expeditianary foray into the world of java servlets. Doing a port would = mean supporting the port for some time. If I were working in this area = (which might happen) I would definitely do it. I'll think about it. = Honestly, it's just install Linux-jdk1.4beta port (I had to hunt that = down on the ftp server), define JAVA_HOME (/usr/local/Linux-jdk1.4beta) = and JAVA_BIN (/usr/local/Linus-jdk1.4beta/bin/java), untar the resin = archive somewhere (/usr maybe) ,from /usr/resin-2.0.0 run configure, = make, make install, cd /usr and "resin-2.0.0/bin/httpd.sh start" and = it's up. It was like 20 minutes time. Also, as I recall Orion installed = ok but fubared when run. I'll try it again and take notes if you like. = (Although I dont have that version of the Linux jdk installed right = now). As a comment from a programmer that has "heard" a great deal about = Java and it's portability, I think it is odd that Java has this much = difficulty with portability. I have less trouble with perl or tcl/tk, = (I'm primarilly a C/C++ programmer). Cross platform portability will = exist if and when pure java apps can in fact be moved between platforms. = I dont see that yet. It might be nice once it happens though. Since this is supposed to be a "platform independent" system, I = really have no choice but to use the lastest from Sun. Using a specific = implementation on a specific OS defeats the purpose IMO. Nice feedback by the way. Thanks.=20 Jim bodkins@prologic.com ------=_NextPart_000_0017_01C100A4.51EB3490 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

Jesse Noller - The problem = that I had=20 with JRun was the depricated version of tar that was used to build = elements of=20 the .sh not JRun itself. I have never managed to untar the thing. I did = install=20 an "old" version of tar and even that didnt work. So whether JRun works = or not,=20 I have no idea. Dead end right now. I tried posting in general JRun = questions on=20 the allaire forum (that cold fusion thingy) but didnt get very = far.

Gabor Kinces - Thanks for = the info.=20 I'll bet you are right about the Hot Spot VM and threads. I tried = posting to the=20 Enhydra lists, but was blocked "for review" or something by a moderator. = Not=20 much help there actually.

Ernst de Haan - A port = should be easy,=20 but this is so far an expeditianary foray into the world of java = servlets. Doing=20 a port would mean supporting the port for some time. If I were working = in this=20 area (which might happen) I would definitely do it. I'll think about it. = Honestly, it's just install Linux-jdk1.4beta port (I had to hunt that = down on=20 the ftp server), define JAVA_HOME (/usr/local/Linux-jdk1.4beta) and = JAVA_BIN=20 (/usr/local/Linus-jdk1.4beta/bin/java), untar the resin archive = somewhere (/usr=20 maybe) ,from /usr/resin-2.0.0 run configure, make, make install, cd /usr = and=20 "resin-2.0.0/bin/httpd.sh start" and it's up. It was like 20 minutes = time. Also,=20 as I recall Orion installed ok but fubared when run. I'll try it again = and take=20 notes if you like. (Although I dont have that version of the Linux jdk = installed=20 right now).

As a comment from a = programmer that=20 has "heard" a great deal about Java and it's portability, I think it is = odd that=20 Java has this much difficulty with portability. I have less trouble with = perl or=20 tcl/tk, (I'm primarilly a C/C++ programmer). Cross platform portability = will=20 exist if and when pure java apps can in fact be moved between platforms. = I dont=20 see that yet. It might be nice once it happens though.

Since this is supposed to = be a=20 "platform independent" system, I really have no choice but to use the = lastest=20 from Sun. Using a specific implementation on a specific OS defeats the = purpose=20 IMO.

Nice feedback by the way. = Thanks.=20

Jim

bodkins@prologic.com

------=_NextPart_000_0017_01C100A4.51EB3490-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message