Is Java really platform-independant? Post: 302606643

Sponsored Content

Top Forums Programming Is Java really platform-independant? Post 302606643 by gabam on Monday 12th of March 2012 10:05:05 AM

03-12-2012

Registered User

My dear friend,
Could you please have a look at wikipedia
Java class file - Wikipedia, the free encyclopedia
which clearly says

Code:

 
In the Java programming language, source files (.java files) are compiled into (virtual) machine-readable class files which have a .class extension. 
Since Java is a platform-independent language, source code is compiled into an output file known as bytecode, which it stores in a .class file. 
If a source file has more than one class, each class is compiled into a separate .class file. These .class files can be loaded by any Java Virtual Machine (JVM). 
JVMs are available for many platforms, and the .class file compiled in one platform will execute in a JVM of another platform. 
This makes Java platform-independent.

What do you say about that?

gabam

View Public Profile for gabam

Find all posts by gabam

LEARN ABOUT SUSE

dacs.java

DACS.JAVA(7)						  DACS Miscellaneous Information					      DACS.JAVA(7)

NAME

       dacs.java - DACS Java support

DESCRIPTION

       This document describes support for Java provided by DACS.

       To enable Java support, DACS must be configured using the --enable-java flag. It may also be necessary to specify the location of the Java
       commands and include files. See dacs.install(7)[1].

	   Note
	   Java support is currently very limited and should be considered experimental. It is currently only possible to call dacsauth(1)[2] and
	   dacscheck(1)[3] using the Java Native Interface (JNI) provided. The command line arguments to both of these commands are exactly as
	   documented in their manual pages. Each argument is passed as a String.

	   The code is not thread-safe and is probably not suitable for being called many times within a particular process due to assumptions it
	   makes about dynamic memory allocation.

	   There are no immediate plans to improve or extend Java support. Using the existing capability to build the JNI layer, however, it
	   should not be difficult for an experienced Java programmer to build upon the example Java code provided.

       With Java support enabled, building DACS will copy the JNI shared library and a .jar file to the library directory (default:
       /usr/local/dacs/lib), and the JNI include files to the include directory (default: /usr/local/dacs/include).

       The tools/java/jni distribution directory contains a simple script called javarun that demonstrates how to run dacsauth or dacscheck as a
       Java application. For example, to validate the Unix password for user somebody, run (as root):

	   ./javarun dacsauth -m unix suff -user somebody -prompt

DIAGNOSTICS

       The return codes are as documented in the command's manual page.

AUTHOR

       Distributed Systems Software (www.dss.ca[4])

COPYING

       Copyright2003-2012 Distributed Systems Software. See the LICENSE[5] file that accompanies the distribution for licensing information.

NOTES

	1. dacs.install(7)
	   http://dacs.dss.ca/man/dacs.install.7.html

	2. dacsauth(1)
	   http://dacs.dss.ca/man/dacsauth.1.html

	3. dacscheck(1)
	   http://dacs.dss.ca/man/dacscheck.1.html

	4. www.dss.ca
	   http://www.dss.ca

	5. LICENSE
	   http://dacs.dss.ca/man/../misc/LICENSE

DACS 1.4.27b							    10/22/2012							      DACS.JAVA(7)