Paul Pantera from Sun has provided us with a very detailed explanation of how to set up your system for this. You can find it in the Quick Fix section of j3d.org. Normally you will only find these errors when running under Java Plugin. There is a known bug with Java Plugin with JDK 1.2 and 1.2.1 that causes the JAR files to be not found and causes the above exceptions To fix this, you need to copy the JAR files from $jre.home/lib/ext to $jre.home/lib. Now your application will find the classes.

For V4R5, see V4R5 5769-JV1 Option 5 (JDK 1.3) AS/400 Install Instructions. This is off of the Java Deployment page. There should also be instructions... I want to use the Developer Kit's native JDBC driver to retrieve data from other AS/400s on a network. I've added the proper Relational Database Entries, but when I try to connect to the remote machines,... If you're at V4R3 or below, the recommendation is to use the Toolbox driver rather than the native driver.

Authored by: Mukul Sabharwal (1) Download JDK 1.4.2 for Linux http://java.sun.com/j2se/1.4.2/download.html --> j2sdk-1_4_2_13-linux-i586.bin (2) Download JDK 1.5.0 sources for Linux http://www.sun.com/software/communitysource/j2se/java2/download.xml --> SCSL Source (jdk-1_5_0-src.scsl.zip) --> SCSL Binaries (jdk-1_5_0-bin.scsl.zip) (3) Download patch files for FreeBSD http://www.eyesbeyond.com/freebsddom/java/jdk15.html --> Patch Level 4 (bsd-jdk15-patches-4.tar.

The easiest way is to use packet manager (eg. for debian apt-get). If you are unsure, follow steps on this page at "How can I install Java (JDK) on Debian?"

Go to address http://java.sun.com/javase/downloads/index.jsp and download packet that contains java JDK and JRE with extension .bin Download it in directory /usr/java (do all steps as root). x@y:/$ mkdir /usr/java x@y:/$ cd /usr/java x@y:/usr/java/$ chmod 755 jdk-1_5_0_09-linux-i586-rpm.bin x@y:/usr/java/$ ./jdk-1_5_0_09-linux-i586-rpm.bin After installation, make and run this script. x@y:/usr/java$ pico skripta.sh #!/bin/sh for i in 'find /usr/java | grep ^.*\.

lt;project> ... <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <verbose>true</verbose> <fork>true</fork> <executable><!-- path-to-javac --></executable> <compilerVersion>1.3</compilerVersion> </configuration> </plugin> </plugins> </build> ... </project>

No. Java 3D requires the use of a number of Java 2 specific features in order to run that cannot be removed. More specifically: Java 3D uses the GraphicsConfiguration classes to get screen information to decide how to do the hardware/software rendering. Java 1.1 does not provide this therefore no implementation of Java 3D will ever run on Java 1.1.

On Windows, Linux, Solaris, and Java 3D 1.5 for Mac OS X, installers are available here: https://java3d.dev.java.net/binary-builds.html

You can get our releases either with a World Wide Web (WWW) browser or by anonymous ftp. For details, including installation instructions, visit: The JavaTM Development Kit (http://java.sun.com/products/jdk/) Choose the version of the JDK you want, and go from there.

Sun's Java 1.3 ORB does not support character sets UTF-8 and UTF-16. To use Sun's Java 1.3 ORB with TAO, you must disable the generation of optional standard profile components in IORs generated by TAO. To do so, use the following ORB initialization option with TAO servers that generate IORs that will be used by Java 1.3 ORB clients: Thanks to Gordana and Kate Matic gordanam@ot.co.nz for posing the original question and Carlos O'Ryan coryan@uci.edu for providing the answer.

Yes, the JDK 1.3.1 is installed on osprey. Note that you do not need this information to run an applet on your homepage. You will only need this information if you want to compile your classes on osprey, use osprey for networking, or run some other stand-alone application. The JDK binaries (e.g., java, javac) are located in /usr/bin. You should place any of your classes in a directory in your account entitled "classes." This is automatically included in the Java CLASSPATH variable.

The JDK, also called the Java Software Development Kit (SDK), is the full suite of tools required to develop, package and publish Java applications. The Sun Java SDK includes the full Java class library, with a compiler, decompiler, profiler, JAR signer, key signing tool and many other tools.

Java3D is a low level 3D scene-graph based graphics programming API for the java language. It does not form part of the core APIs required by the Java specification. The class libraries exist under the javax.media.j3d top level package as well as utility classes provided in javax.vecmath. A low level API provides routines for creation of 3D geometeries in a scenegraph structure that is independent of the underlying hardware implementation for realtime programming.

If you want to distribute the files with your own setup file, please visit our website [2] for an installation script source code. You can then modify this installer for your own needs or simply use it to learn how the software is installed. You can run the original setup file using command line switches to control the behaviour of the installer.

In other words, as long as the Java3D classes are installed properly and available, Java 3D applications are invoked in the exact same manner as other applications. The following questions still need someone to write an answer for them. When this is done, they can be moved back up to the previous section in the appropriate place.

We found the question of installation so troublesome with mismatch of versions and users patially installing the software we bundle the complete java jvm and libraries (including J3D?) and in a subdirectory of our installation directory. No troubles since we did that. Topic Java3DFAQ .

Java 1.3 is no longer supported, and DrJava is compiled to require Java 1.4 or later. However, you can use an older version of DrJava. drjava-stable-20040326 was the last stable release to support Java 1.3.

Include the JDBC 2.0 classes in the applet's classpath. Why? Because Netscape's class verifier is overly strict and tries to verify the existence of all referenced classes, even ones that the user's application never uses. It is enough that they are in the Toolbox jar file. Since the Toolbox supports JDBC 2.0, and the 2.0 classes are referenced in the Toolbox, but are not available in the applet's 1.1.x JVM, then the verifier throws an error. We ship stubs for the JDBC 2.0 classes in jtStubs.

Note: unless you want to work with the Java 3D internals, or see automated source code checkin messages, you only need to join the parent java3d project. The new Java 3D interest list is available either as a discussion forum (which is what most of the community uses) or as a mailing list. Messages posted to one are cross-posted to the other automatically. Go to the "Mailing Lists" page of the parent java3d project and subscribe to the "interest@java3d.dev.java.

Before downloading the source code, you will need to create a java.net account if you don't already have one. You must use CVS to download the source code for projects on java.net (see: Q: What is CVS and How Do I Use It? if you are unfamiliar with CVS). Java 3D is composed of three main CVS modules (projects), which can be checked out using a CVS client: In order to build the code, the three top-level directories must be named exactly as shown above and they must be sibling directories.

Download the source code for the following three projects: j3d-core, j3d-core-utils, and vecmath (see Q: How do I download the Java 3D source code?)

Whatever you make of it. Sun has now released the source code to Java3D as a project under the Java.net site. The license is split between BSD for the utility code, and a SCSL-like license for the core runtime and vecmath parts. The current version of all the code is available in CVS, details of which can be found at the various subproject pages. Java3D is now being developed as an open project (but not open source) through the java.net development group. 1.4.

Java3D is another 3D programming API that exists on a similar level to OpenGL, Direct3D, PHIGS and similar systems. It is designed to use hardware accelaration wherever possible based on the underlying graphics architecture of the OS. That is, J3D provides a 3D rendering API for the Java language, but at the same time it may use OpenGL to do the interface to the hardware.

j3d.org maintains a list of sites that use Java 3D as well as a number of other interesting Java 3D related links. Please visit it! Java3D is being used in many different application environments. There's a highly publicised use of J3D in a CAVE in Canada (see Sun's Java3D homepage for a link to the whitepaper) down to the PC. We're not aware of J3D being used in small footprint devices like PDAs and mobile phones.

There are two ways of accomplishing this. The first is to use JDK 1.4 or later. These have API calls for creating fullscreen windows directly. If you need to use an earlier version of the JDK, then follow these instructions: PREFERRED - fullscreen mode is preferred. Try to initiate fullscreen mode but if that fails, use a regular window instead. For instance, to run the HelloUniverse example program in fullscreen mode if it is available, the following command would be used: java -Dj3d.

Please click here or refer to "Setting up your computer" for a step by step help on setting up your computer.

If you tested for the Java software and do not have it installed on your computer, you can download it for free by clicking here. If the page is fully loaded and you do not see a field to enter a screen name, your browser is not supporting the Java software. Click here to download Java for free.

The size of the String, when UTF-encoded, must be < 64Kb So for robust code you have to examine the String once to ensure that it will be less than 64Kb after encoding, and then have the JVM effectively repeat that work in the process of encoding, when you write it to an ObjectOutputStream. A possible workaround that is to strip the string down to "byte[]" and pass it around in RMI that way. The code with this restriction is in DataOutputStream public final void writeUTF(String str) ..