java runtime environment
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 4079
Java 2 Standard Edition Runtime Environment 6u2
Java 2 SE Runtime Environment 6 offers a feature complete version of Suns next major release of the Java SE platform. more>>
Java 2 Standard Edition Runtime Environment 6 (Mustang) offers a feature complete version of Suns next major release of the Java SE platform.
Sun has endeavored to foster the highest level of transparency and collaboration on the platform with the Java community through the Mustang Project, and expects to ship the final release of Java SE 6 the fall of 2006.
Main features:
New Security features and enhancements:
- Native platform GSS/Kerberos integration
- Java Authentication and Authorization Service (JAAS) login module that employs LDAP authentication
- New Smart Card I/O API
Integrated Web Services:
- New API for XML digital signature services for secure web services
- New Client and Core Java Architecture for XML-Web Services (JAX-WS) 2.0 APIs
- New support for Java Architecture for XML Binding (JAXB) 2.0
Enhanced Management & Serviceability:
- Improved JMX Monitoring API
- Runtime Support for dTrace (Solaris 10 and future Solaris OS releases only)
- New custom deployment facilities
Increased Developer Productivity:
- Improved memory usage analysis and leak detection
- Significant library improvements
- Improvements to the Java Platform Debug Architecture (JPDA) & JVM Tool Interface
Improved User Experience:
- Look and feel updates to better match underlying platforms
- Improved desktop performance and integration
- Enhanced internationalization support
<<lessSun has endeavored to foster the highest level of transparency and collaboration on the platform with the Java community through the Mustang Project, and expects to ship the final release of Java SE 6 the fall of 2006.
Main features:
New Security features and enhancements:
- Native platform GSS/Kerberos integration
- Java Authentication and Authorization Service (JAAS) login module that employs LDAP authentication
- New Smart Card I/O API
Integrated Web Services:
- New API for XML digital signature services for secure web services
- New Client and Core Java Architecture for XML-Web Services (JAX-WS) 2.0 APIs
- New support for Java Architecture for XML Binding (JAXB) 2.0
Enhanced Management & Serviceability:
- Improved JMX Monitoring API
- Runtime Support for dTrace (Solaris 10 and future Solaris OS releases only)
- New custom deployment facilities
Increased Developer Productivity:
- Improved memory usage analysis and leak detection
- Significant library improvements
- Improvements to the Java Platform Debug Architecture (JPDA) & JVM Tool Interface
Improved User Experience:
- Look and feel updates to better match underlying platforms
- Improved desktop performance and integration
- Enhanced internationalization support
Download (17.6MB)
Added: 2007-07-08 License: SUN Community Source License Price:
843 downloads
Java 2 Standard Edition Runtime Environment 1.5.0 Update 12
Java 2 Platform, Standard Edition (J2SE) software is the premier platform for rapidly developing. more>>
Java 2SE technology readily harnesses the power of the network because it is both a programming language and a selection of specialized platforms.
As such, it standardizes the development and deployment of the kind of secure, portable, reliable, and scalable applications required by the networked economy.
Because the Internet and World Wide Web play a major role in new business development, consistent and widely supported standards are critical to growth and success.
The Java programming language lets you write powerful, enterprise-worthy programs that run in the browser, from the desktop, on a server, or on a consumer device. Java programs are run on -- interpreted by -- another program called the Java Virtual Machine (Java VM).
Rather than running directly on the native operating system, the program is interpreted by the Java VM for the native operating system. This means that any computer system with the Java VM installed can run a Java program regardless of the computer system on which the application was originally developed.
The Java platform is a software-only platform that runs on top of other hardware-based platforms. Because hardware-based platforms vary in their storage, memory, network connection, and computing power capabilities, specialized Java platforms are available to address applications development for and deployment to those different environments.
Java technology has grown to include the portfolio of specialized platforms listed below. Each platform is based on a Java VM that has been ported to the target hardware environment. This means, for example, in the case of Desktop Java, desktop applications written in the Java programming language can run on any Java VM-enabled desktop without modification.
Java 2 Platform, Standard Edition (J2SE), provides an environment for Core Java and Desktop Java applications development, and is the basis for Java 2 Platform, Enterprise Edition (J2EE) and Java Web Services technologies. It has the compiler, tools, runtimes, and Java APIs that let you write, test, deploy, and run applets and applications.
Enhancements:
- Olson time zone data was updated to version 2007e.
- Solaris-specific I/O interruption in response to thread interruption can now be switched off.
- Many bugs were fixed.
<<lessAs such, it standardizes the development and deployment of the kind of secure, portable, reliable, and scalable applications required by the networked economy.
Because the Internet and World Wide Web play a major role in new business development, consistent and widely supported standards are critical to growth and success.
The Java programming language lets you write powerful, enterprise-worthy programs that run in the browser, from the desktop, on a server, or on a consumer device. Java programs are run on -- interpreted by -- another program called the Java Virtual Machine (Java VM).
Rather than running directly on the native operating system, the program is interpreted by the Java VM for the native operating system. This means that any computer system with the Java VM installed can run a Java program regardless of the computer system on which the application was originally developed.
The Java platform is a software-only platform that runs on top of other hardware-based platforms. Because hardware-based platforms vary in their storage, memory, network connection, and computing power capabilities, specialized Java platforms are available to address applications development for and deployment to those different environments.
Java technology has grown to include the portfolio of specialized platforms listed below. Each platform is based on a Java VM that has been ported to the target hardware environment. This means, for example, in the case of Desktop Java, desktop applications written in the Java programming language can run on any Java VM-enabled desktop without modification.
Java 2 Platform, Standard Edition (J2SE), provides an environment for Core Java and Desktop Java applications development, and is the basis for Java 2 Platform, Enterprise Edition (J2EE) and Java Web Services technologies. It has the compiler, tools, runtimes, and Java APIs that let you write, test, deploy, and run applets and applications.
Enhancements:
- Olson time zone data was updated to version 2007e.
- Solaris-specific I/O interruption in response to thread interruption can now be switched off.
- Many bugs were fixed.
Download (15.7MB)
Added: 2007-06-12 License: SUN Community Source License Price:
635 downloads
Java Development Environment for Emacs 2.3.5
Java Development Environment for Emacs is a complete Java development environment for Emacs. more>>
Java Development Environment for Emacs (JDEE) is an Emacs-based integrated development environment (IDE) for developing Java applications and applets.
Features include multiple code browsers, a JPDA-based debugger, method and field completion, template-based and procedure-based code generation, Java source code interpreter, context-sensitive help, and more.
Enhancements:
- On XEmacs, Use efc-xemacs-query-options, i.e., a GUI dialog box instead of a text dialog box, only if use-dialog-box is nonnil.
- Fixes bug in ProjectClasses to avoid duplicate entries of imports.
- Updated JDEEs Ant interface to force use of pipes to interact with external Ant process.
- Fixed regression that caused jde-help-class-member to issue a Lisp error.
- Fixed regression in jde-wiz-update-class-list command.
- Fixed regression that caused JDEbug to issue a Lisp error when launching an application.
- Thanks to Martin Schwamberger.
- Revise the following templates to conform to CheckStyle requirements:
- jde-gen-deep-clone-template
- jde-gen-to-string-method-template
- jde-gen-bean-template
- Thanks to Martin Schwamberger.
- Added the following code generation templates:
- jde-gen-exception
- Generates an exception class in the current buffer.
- jde-gen-exception-buffer
- Generates a buffer containing an exception class.
- jde-gen-hashcode-method
- Generates a hashcode method at point.
- jde-gen-equals-method
- Generates an equals method at point.
- jde-gen-tostring-method
- Generates a toString method that uses Apaches
- ToStringBuilder class.
- Thanks to Ole Arndt.
- Enhanced jde-run-option-classpath to allow you to specify that the JDEE should omit the classpath argument when running the class or application in the current buffer, regardless of the setting of jde-global-classpath.
- Fixed regression that caused the JDEE to switch projects during debugging when stepping into code that does not belong to the project being debugged.
- Updated regular expressions used by the JDEEs interface to jdb to accommodate non-English punctuation styles for numeric expressions in debugger messages, e.g.,
- 1.200 for a line number where the English would write 1,200.
- Thanks to Morten B. Isaksen.
- In previous releases, building javadoc caused all future uses of compilation mode to try to
- display the javadoc. This release fixes the problem.
- Thanks to David Evers.
- Updated the submit-problem-report command to include an XEmacs users init.el file.
<<lessFeatures include multiple code browsers, a JPDA-based debugger, method and field completion, template-based and procedure-based code generation, Java source code interpreter, context-sensitive help, and more.
Enhancements:
- On XEmacs, Use efc-xemacs-query-options, i.e., a GUI dialog box instead of a text dialog box, only if use-dialog-box is nonnil.
- Fixes bug in ProjectClasses to avoid duplicate entries of imports.
- Updated JDEEs Ant interface to force use of pipes to interact with external Ant process.
- Fixed regression that caused jde-help-class-member to issue a Lisp error.
- Fixed regression in jde-wiz-update-class-list command.
- Fixed regression that caused JDEbug to issue a Lisp error when launching an application.
- Thanks to Martin Schwamberger.
- Revise the following templates to conform to CheckStyle requirements:
- jde-gen-deep-clone-template
- jde-gen-to-string-method-template
- jde-gen-bean-template
- Thanks to Martin Schwamberger.
- Added the following code generation templates:
- jde-gen-exception
- Generates an exception class in the current buffer.
- jde-gen-exception-buffer
- Generates a buffer containing an exception class.
- jde-gen-hashcode-method
- Generates a hashcode method at point.
- jde-gen-equals-method
- Generates an equals method at point.
- jde-gen-tostring-method
- Generates a toString method that uses Apaches
- ToStringBuilder class.
- Thanks to Ole Arndt.
- Enhanced jde-run-option-classpath to allow you to specify that the JDEE should omit the classpath argument when running the class or application in the current buffer, regardless of the setting of jde-global-classpath.
- Fixed regression that caused the JDEE to switch projects during debugging when stepping into code that does not belong to the project being debugged.
- Updated regular expressions used by the JDEEs interface to jdb to accommodate non-English punctuation styles for numeric expressions in debugger messages, e.g.,
- 1.200 for a line number where the English would write 1,200.
- Thanks to Morten B. Isaksen.
- In previous releases, building javadoc caused all future uses of compilation mode to try to
- display the javadoc. This release fixes the problem.
- Thanks to David Evers.
- Updated the submit-problem-report command to include an XEmacs users init.el file.
Download (3.6MB)
Added: 2005-04-03 License: GPL (GNU General Public License) Price:
1671 downloads
Java Binary Enhancement Tool 3 R1
Java Binary Enhancement Tool is a Java assembler, dissassembler, and binary editor. more>>
The Java Binary Enhancement Tool (JBET) is a general Java program analysis and manipulation tool. Existing class files can be disassembled, reassembled, or edited programmatically through the JBET API. JBET can also be used to create new Java class files from scratch. JBET uses a convenient internal representation of all the contents of Java binary (.class) files, allowing the user to edit the classes easily, in a structured manner.
JBET was developed as part of the DARPA Self-Protecting Mobile Agents project under the OASIS and Active Networks programs (contract number N66001-00-C-8602) in order to study automated software obfuscation.
The Java language was chosen for this project because of the (relative) ease of constructing binary editing tools provided by the large amount of type information present in the class files. Our two reports, the Obfuscation Techniques Evaluation Report, and the Obfuscation Report, are available from the download area. The obfuscation tool developed is not part of this release.
JBET was also used in the DARPA/AFRL Survivable Server project (contract number F30602-00-C-0183) to add additional security checks to the Java Standard Library. (The Java SecurityManager API does not support many desirable security checks, such as continued authorization of file accesses after opening.)
JBET was used to replace the native method references in the Java standard library with stubs that call a pluggable security policy. This tool, called Jpolicy, is also available for download at this website. Jpolicy is very incomplete at this time, but may be interesting to those working in Java security or changing the standard library themselves.
The internal representation of Java class files used by JBET is intented to make it easy for programmers to write Java binary code transforms. Each element of Java class files has a corresponding internal data structure: ClassInfo for entire classes, MethodInfo for methods, FieldInfo for fields, Snippit for code blocks, and Instruction for individual instructions. Snippit and Instruction understand Java opcode syntax and semantics, allowing automated creation of valid Java programs. A Java-compatible class verifier is also included.
Some code transforms are difficult to program directly by manipulating Java instructions. For those transforms, a directed acyclic graph (DAG) representation of code is available. In the DAG representation, each basic block has a corresponding DAG, with a set of input and output nodes. Edges in the graph connect "producer" nodes (such as constants, or the result of calculations) to "user" nodes (such as method calls or other calculations). Methods are divided into basic blocks and control flow is stored at the basic block level (possible because Java has only fixed jump targets)
JBET requires a Java 1.4 virtual machine to run, although it can operate on class files from earlier Java versions. The packaging and build environment supplied supports Linux and Windows with Cygwin; however, the build process is simple and could be performed manually on other platforms. Perl is required for regression testing.
Jpolicy requires a Java 1.4 virtual machine to build, either Linux or Windows NT/XP with Cygwin. gcc is required for building on Windows (supplied with Cygwin). The runtime system can be either Java 1.3 or 1.4 (with Suns JVM only), running on Linux or Windows NT/XP. Windows 9x and Windows 2000 may work as well, but have not been tested.
Installation
1. Install jdk 1.4.1.
2. Set CLASSPATH to jdk1.4.1/jre/lib/rt.jar
3. cd src; make
4. If that didnt work, examine the makefile. java or javac may not be in the path.
5. To build a jar file that can be used with "java -jar jbet.jar", run "make jar".
6. If you have perl installed, run the tests with "make test".
Optionally, run "make regen; make test".
Make a symbolic link from jbet3/bin/jbet to somewhere in your path.
Usage
JBET uses the JNI format for class names, and JNI type and method descriptors. For a summary of this syntax, use jbet help syntax. Suns JVM specification may also be helpful.
To look at a class disassembly, use jbet print. Try disassembling a class you have source for, and was built with debug info (-g): jbet -P < classpath > print < classname >. Suns JVM specification has an instruction reference.
<<lessJBET was developed as part of the DARPA Self-Protecting Mobile Agents project under the OASIS and Active Networks programs (contract number N66001-00-C-8602) in order to study automated software obfuscation.
The Java language was chosen for this project because of the (relative) ease of constructing binary editing tools provided by the large amount of type information present in the class files. Our two reports, the Obfuscation Techniques Evaluation Report, and the Obfuscation Report, are available from the download area. The obfuscation tool developed is not part of this release.
JBET was also used in the DARPA/AFRL Survivable Server project (contract number F30602-00-C-0183) to add additional security checks to the Java Standard Library. (The Java SecurityManager API does not support many desirable security checks, such as continued authorization of file accesses after opening.)
JBET was used to replace the native method references in the Java standard library with stubs that call a pluggable security policy. This tool, called Jpolicy, is also available for download at this website. Jpolicy is very incomplete at this time, but may be interesting to those working in Java security or changing the standard library themselves.
The internal representation of Java class files used by JBET is intented to make it easy for programmers to write Java binary code transforms. Each element of Java class files has a corresponding internal data structure: ClassInfo for entire classes, MethodInfo for methods, FieldInfo for fields, Snippit for code blocks, and Instruction for individual instructions. Snippit and Instruction understand Java opcode syntax and semantics, allowing automated creation of valid Java programs. A Java-compatible class verifier is also included.
Some code transforms are difficult to program directly by manipulating Java instructions. For those transforms, a directed acyclic graph (DAG) representation of code is available. In the DAG representation, each basic block has a corresponding DAG, with a set of input and output nodes. Edges in the graph connect "producer" nodes (such as constants, or the result of calculations) to "user" nodes (such as method calls or other calculations). Methods are divided into basic blocks and control flow is stored at the basic block level (possible because Java has only fixed jump targets)
JBET requires a Java 1.4 virtual machine to run, although it can operate on class files from earlier Java versions. The packaging and build environment supplied supports Linux and Windows with Cygwin; however, the build process is simple and could be performed manually on other platforms. Perl is required for regression testing.
Jpolicy requires a Java 1.4 virtual machine to build, either Linux or Windows NT/XP with Cygwin. gcc is required for building on Windows (supplied with Cygwin). The runtime system can be either Java 1.3 or 1.4 (with Suns JVM only), running on Linux or Windows NT/XP. Windows 9x and Windows 2000 may work as well, but have not been tested.
Installation
1. Install jdk 1.4.1.
2. Set CLASSPATH to jdk1.4.1/jre/lib/rt.jar
3. cd src; make
4. If that didnt work, examine the makefile. java or javac may not be in the path.
5. To build a jar file that can be used with "java -jar jbet.jar", run "make jar".
6. If you have perl installed, run the tests with "make test".
Optionally, run "make regen; make test".
Make a symbolic link from jbet3/bin/jbet to somewhere in your path.
Usage
JBET uses the JNI format for class names, and JNI type and method descriptors. For a summary of this syntax, use jbet help syntax. Suns JVM specification may also be helpful.
To look at a class disassembly, use jbet print. Try disassembling a class you have source for, and was built with debug info (-g): jbet -P < classpath > print < classname >. Suns JVM specification has an instruction reference.
Download (0.19MB)
Added: 2005-03-07 License: BSD License Price:
1697 downloads
Cell Electrophysiology Simulation Environment 1.4.6
Cell Electrophysiology Simulation Environment is a simulation environment for electrophysiology. more>>
Cell Electrophysiology Simulation Environment (CESE) is a comprehensive framework specifically designed to perform computational electrophysiological simulations, for example, simulations of cardiac myocyte electrical activity.
Cell Electrophysiology Simulation Environment is useful for simulations of action potentials, individual ionic currents, and changes in ionic concentrations.
CESE is a cross-platform program, it runs on any system that has Java runtime environment (JRE) version 1.4 or above. It was tested on Windows, Linux, Solaris, MacOS X, and AIX.
CESE users
CESE is an integrated environment for performing computational simulations using a variety of electrophysiological models.
At this stage CESE allows creation and execution of the single-cell models (containing both Hodgkin-Huxley (HH) and Markovian current formulations). Models of electrical activity of cardiac myocytes with source code are included in the CESE distribution. We hope to extend the number of available models, and add certain neuronal models in the future.
The main strength of CESE is in its uniformity ? a program interface remains the same for different types of models. You can easily switch between models and compare simulation outputs. Model parameters can be modified, selected for output and/or clamped in the same, standard way.
CESE extends the conventional electrophysiological meaning of the "voltage clamp". You can clamp virtually any model variable, including voltage (membrane potential), total or individual ionic currents, ionic concentrations, temperature, gating variables, etc. The clamping commands can be complex piece-wise functions, individually set for the model variable of interest. This opens endless possibilities for the exploration of complex model behavior.
CESE provides simple, but efficient data visualizations. Simulation results can be presented in the graphic and tabulated forms. Plots can be customized, and regions of interest zoomed.
Even though CESE was not designed to be a data analysis tool, you can generate current-voltage relationships (I-Vs) and calculate statistical parameters for a given signal within the program. You can export your data to ASCII, Axon Text File (ATF), and NetCDF formats to continue analysis in your favorite package.
CESE developers
CESE was created from the ground up to incorporate the best programming practices available to Java developers, both in terms of user interface consistency and code clarity and reuse. Wherever possible, CESE rely on available Java APIs (for example Java2D, JavaBeans, JAXP) to simplify the code.
Model creation requires a number of house-keeping functions to be coded ? these include ODE integrators, routines for handling model parameters, saving/restoring model state, visualizing simulation results, etc. CESE provides you with implementation for these routines, hence, you can concentrate on writing the code for concrete ionic current(s), and CESE will handle the rest.
CESE is not trying to create complicated programming frameworks on its own ? rather, it utilizes core Java APIs. For example, models are Java components conforming to the JavaBeans specification. We use XML to specify clamping commands, and Java object serialization to save/restore model parameters.
Enhancements:
- This release improves results printing, adds export to the scalable vector graphics (SVG) format, improves support for continuous simulations, and fixes many bugs in plot rendering and model switching.
<<lessCell Electrophysiology Simulation Environment is useful for simulations of action potentials, individual ionic currents, and changes in ionic concentrations.
CESE is a cross-platform program, it runs on any system that has Java runtime environment (JRE) version 1.4 or above. It was tested on Windows, Linux, Solaris, MacOS X, and AIX.
CESE users
CESE is an integrated environment for performing computational simulations using a variety of electrophysiological models.
At this stage CESE allows creation and execution of the single-cell models (containing both Hodgkin-Huxley (HH) and Markovian current formulations). Models of electrical activity of cardiac myocytes with source code are included in the CESE distribution. We hope to extend the number of available models, and add certain neuronal models in the future.
The main strength of CESE is in its uniformity ? a program interface remains the same for different types of models. You can easily switch between models and compare simulation outputs. Model parameters can be modified, selected for output and/or clamped in the same, standard way.
CESE extends the conventional electrophysiological meaning of the "voltage clamp". You can clamp virtually any model variable, including voltage (membrane potential), total or individual ionic currents, ionic concentrations, temperature, gating variables, etc. The clamping commands can be complex piece-wise functions, individually set for the model variable of interest. This opens endless possibilities for the exploration of complex model behavior.
CESE provides simple, but efficient data visualizations. Simulation results can be presented in the graphic and tabulated forms. Plots can be customized, and regions of interest zoomed.
Even though CESE was not designed to be a data analysis tool, you can generate current-voltage relationships (I-Vs) and calculate statistical parameters for a given signal within the program. You can export your data to ASCII, Axon Text File (ATF), and NetCDF formats to continue analysis in your favorite package.
CESE developers
CESE was created from the ground up to incorporate the best programming practices available to Java developers, both in terms of user interface consistency and code clarity and reuse. Wherever possible, CESE rely on available Java APIs (for example Java2D, JavaBeans, JAXP) to simplify the code.
Model creation requires a number of house-keeping functions to be coded ? these include ODE integrators, routines for handling model parameters, saving/restoring model state, visualizing simulation results, etc. CESE provides you with implementation for these routines, hence, you can concentrate on writing the code for concrete ionic current(s), and CESE will handle the rest.
CESE is not trying to create complicated programming frameworks on its own ? rather, it utilizes core Java APIs. For example, models are Java components conforming to the JavaBeans specification. We use XML to specify clamping commands, and Java object serialization to save/restore model parameters.
Enhancements:
- This release improves results printing, adds export to the scalable vector graphics (SVG) format, improves support for continuous simulations, and fixes many bugs in plot rendering and model switching.
Download (5.0MB)
Added: 2007-02-12 License: GPL (GNU General Public License) Price:
587 downloads
Java Brainfuck Compiler 2.0
Java Brainfuck Compiler is an optimising Brainfuck to Java bytecode compiler. more>>
The Java Brainfuck Compiler is a compiler for the uniquely powerful Brainfuck language, which produces Java bytecode that will run on any Java Virtual Machine (with no intermediate steps such as going by way of Java code).
<<less Download (0.010MB)
Added: 2005-04-18 License: GPL (GNU General Public License) Price:
1682 downloads
Java Gui Builder 0.6.5a
Java Gui Builder it decouples your GUI building code from the rest of your application using XML. more>>
The Java Gui Builder program is designed to decouple the GUI building code from the rest of the application code, without hand-writing code.
It allows one to describe the layout of windows and controls using an XML file. A full DTD was written to allow on-the-fly validation.
Using an XML file to describe GUI components allows users the flexibility to rewrite their windows so that they suit their needs, without opening up the innards of the program to the users.
Java Gui Builder can run on any Swing enabled J2SE platform. JGB was tested against Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_08-b03) and Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01). If you want to build JGB, you will need J2SE 1.4 or better. It is not possible to build on 1.3, but can be used on 1.3.
<<lessIt allows one to describe the layout of windows and controls using an XML file. A full DTD was written to allow on-the-fly validation.
Using an XML file to describe GUI components allows users the flexibility to rewrite their windows so that they suit their needs, without opening up the innards of the program to the users.
Java Gui Builder can run on any Swing enabled J2SE platform. JGB was tested against Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_08-b03) and Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01). If you want to build JGB, you will need J2SE 1.4 or better. It is not possible to build on 1.3, but can be used on 1.3.
Download (0.68MB)
Added: 2005-04-18 License: GPL (GNU General Public License) Price:
3156 downloads
Bitgate Server Software Environment 0.4.3
Bitgate Server Software Environment aims to build a multi-protocol environment. more>>
Bitgate Server Software Environment aims to build a multi-protocol environment in which server protocol handlers can be eventually loaded and unloaded on the fly using a center console or controller Web page.
Bitgate Server Software Environment aims to have 99.9% uptime, and have high-availability (Java 6) compliance. It is written in Java 5, and relies completely on Javas I/O functionality to provide non-blocking support for both SSL and non-SSL sockets (transparently).
All configuration is done via XML files, as this is easier to maintain. It includes a minimal demonstration HTTP server.
Enhancements:
- Modified HTTP directory listing to be a little more clean on the output of filenames; shows more information about each file in question as well.
- Added "reset" methods to the ClientContext objects so that Keep-Alive requests are now handled properly.
- Implemented 302 redirects and space encodings on filenames.
<<lessBitgate Server Software Environment aims to have 99.9% uptime, and have high-availability (Java 6) compliance. It is written in Java 5, and relies completely on Javas I/O functionality to provide non-blocking support for both SSL and non-SSL sockets (transparently).
All configuration is done via XML files, as this is easier to maintain. It includes a minimal demonstration HTTP server.
Enhancements:
- Modified HTTP directory listing to be a little more clean on the output of filenames; shows more information about each file in question as well.
- Added "reset" methods to the ClientContext objects so that Keep-Alive requests are now handled properly.
- Implemented 302 redirects and space encodings on filenames.
Download (0.057MB)
Added: 2007-08-06 License: Common Public License Price:
811 downloads
Runtime Java Class Editor 1.0
Runtime Java Class Editor is a tool for editing loaded (running) Java classes and much more. more>>
RJCE allows all methods or variables of user defined classes to be altered at runtime. These alterations are then applied to a single instance, a collection of instances (i.e. list, set or map), or an entire class.
This helps you to test your application in an interactive way; altering running programs helping a trial and error approach to programming; testing code and saving it when its correct. Long running algorithms, such as simulations, can also easily be refined without the need for restarts or lose of data.
RJCE can be used to write a program from within itself ensuring high coupling between testing and development, with no delay before the outcome of any alterations.
RJCE allows scripts to run from within your application, allowing users to configure or extend an application dynamically, bypassing normal language access rules controlled by public, private and protected. This can be done by easily instatiating an instance of CodeEditorFrame from the rom.gui package.
RJCE permits faster development of applications by allowing easy migration from scripts to Java programs.
<<lessThis helps you to test your application in an interactive way; altering running programs helping a trial and error approach to programming; testing code and saving it when its correct. Long running algorithms, such as simulations, can also easily be refined without the need for restarts or lose of data.
RJCE can be used to write a program from within itself ensuring high coupling between testing and development, with no delay before the outcome of any alterations.
RJCE allows scripts to run from within your application, allowing users to configure or extend an application dynamically, bypassing normal language access rules controlled by public, private and protected. This can be done by easily instatiating an instance of CodeEditorFrame from the rom.gui package.
RJCE permits faster development of applications by allowing easy migration from scripts to Java programs.
Download (3.1MB)
Added: 2005-04-18 License: BSD License Price:
1713 downloads
Java-Gnome 4.0.3
Java-GNOME is a set of Java bindings for the GNOME and GTK libraries. more>>
Java-GNOME application is a set of Java bindings for the GNOME and GTK libraries that allow GNOME and GTK applications to be written in Java.
The Java-Gnome API has been carefully designed to be easy to use, maintaining a good OO paridigm, yet still wrapping the entire functionality of the underlying libraries.
Java-Gnome can be used with the Eclipse development environment and Glade user interface designer to create applications with ease.
Java-Gnome is part of the official Gnome Bindings Release, commiting us to high quality regular releases.
<<lessThe Java-Gnome API has been carefully designed to be easy to use, maintaining a good OO paridigm, yet still wrapping the entire functionality of the underlying libraries.
Java-Gnome can be used with the Eclipse development environment and Glade user interface designer to create applications with ease.
Java-Gnome is part of the official Gnome Bindings Release, commiting us to high quality regular releases.
Download (0.17MB)
Added: 2007-07-31 License: GPL (GNU General Public License) Price:
815 downloads
Java Properties 0.8.3
Java Properties provides an efficient way to access bean-like properties of Java objects. more>>
Java Properties provides an efficient way to access bean-like properties of Java objects.
In a nutshell, provides an efficient way to access bean-like properties of java objects. Unlike java bean properties, a chain of properties can be specified efficiently, allowing convenient access to properties of nested domain objects.
Runtime class-generation and caching can be used very easily to obviate the need for reflection, without losing the flexibility it provides.
Class Properties It also provides classes which manipulate objects at runtime by using strings to address conceptual variables (think bean properties) in a similar fashion to the java reflection mechanisms.
Class Property example Say we have the following classes:
public class Order {
...
public Customer getCustomer() { ... }
...
}
public class Customer {
...
public Address getAddress() { ... }
...
}
public class Address {
...
public String getLine1() { ... }
public String getLine2() { ... }
...
}
Now, we could do this to access line 1 of the address:
result = order.getCustomer().getAddress().getLine1();
But what if there are nulls? What if we want to compare the first line of the address from two different orders? Whith properties this is really simple:
ClassProperty p = PropertyManager.getProperty(Order.class,"Customer:Address:Line1",true);
result = p.getValue(order);
The idea is simple enough - you use the string "Customer:Address:Line1" to specify a series of getXXX calls. Importantly, it the library handles nulls for you, returning null if any of the objects in the chain are null.
Note, this is not simply a wrapper around java reflection, since it includes non-reflective optimizations by making use of the cojen library to generate class files at runtime to acces these properties.
The real benefit lies in being able to specify which properties you wish to access at runtime. You can even pass this ability on to the users of your library or application. Unlike reflection, class files are generated for the properties, and these files are cached - which means once you have specified a property once, further uses of the same property dont use reflection and are very fast.
Property API vs Java Bean Properties. The property API models accessor/mutator method pairs as conceptual variables called properties. The approach used is similar to, but more flexible than java bean properties, and more performant than reflection if runtime class generation is used. Unlike java bean properties, a chain or path of properties can be specified (and more importantly, turned into bytecode using runtime generation) to traverse a complex tree of objects.
It is simple to create applications portable between different security environments - using runtime generation where allowed, and falling back to reflection where security is tighter.
Dynamic Class Management. The properties package also provides classes to handle the loading (and unloading/reloading) of classes at runtime. It provides a framework useful for dynamically loading runtime-generated classes, for example.
While the property API can happily ignore the dynamic loading framework, it can also make use of it to enable runtime class generation.
<<lessIn a nutshell, provides an efficient way to access bean-like properties of java objects. Unlike java bean properties, a chain of properties can be specified efficiently, allowing convenient access to properties of nested domain objects.
Runtime class-generation and caching can be used very easily to obviate the need for reflection, without losing the flexibility it provides.
Class Properties It also provides classes which manipulate objects at runtime by using strings to address conceptual variables (think bean properties) in a similar fashion to the java reflection mechanisms.
Class Property example Say we have the following classes:
public class Order {
...
public Customer getCustomer() { ... }
...
}
public class Customer {
...
public Address getAddress() { ... }
...
}
public class Address {
...
public String getLine1() { ... }
public String getLine2() { ... }
...
}
Now, we could do this to access line 1 of the address:
result = order.getCustomer().getAddress().getLine1();
But what if there are nulls? What if we want to compare the first line of the address from two different orders? Whith properties this is really simple:
ClassProperty p = PropertyManager.getProperty(Order.class,"Customer:Address:Line1",true);
result = p.getValue(order);
The idea is simple enough - you use the string "Customer:Address:Line1" to specify a series of getXXX calls. Importantly, it the library handles nulls for you, returning null if any of the objects in the chain are null.
Note, this is not simply a wrapper around java reflection, since it includes non-reflective optimizations by making use of the cojen library to generate class files at runtime to acces these properties.
The real benefit lies in being able to specify which properties you wish to access at runtime. You can even pass this ability on to the users of your library or application. Unlike reflection, class files are generated for the properties, and these files are cached - which means once you have specified a property once, further uses of the same property dont use reflection and are very fast.
Property API vs Java Bean Properties. The property API models accessor/mutator method pairs as conceptual variables called properties. The approach used is similar to, but more flexible than java bean properties, and more performant than reflection if runtime class generation is used. Unlike java bean properties, a chain or path of properties can be specified (and more importantly, turned into bytecode using runtime generation) to traverse a complex tree of objects.
It is simple to create applications portable between different security environments - using runtime generation where allowed, and falling back to reflection where security is tighter.
Dynamic Class Management. The properties package also provides classes to handle the loading (and unloading/reloading) of classes at runtime. It provides a framework useful for dynamically loading runtime-generated classes, for example.
While the property API can happily ignore the dynamic loading framework, it can also make use of it to enable runtime class generation.
Download (0.017MB)
Added: 2007-01-10 License: GPL (GNU General Public License) Price:
1017 downloads
Java Embedded Python 2.2
Java Embedded Python embeds CPython in Java. more>>
Java Embedded Python embeds CPython in Java. It is safe to use in a heavily threaded environment, it is quite fast and its stability is a main feature and goal.
Main features:
- Using the native Python interpreter may mean a massive speed improvement over Java-based languages.
- Python is mature so authors neednt fear the interpreter will suddenly change widely-used features.
- Access to the high quality Python modules, both native and Python-based.
- Compilers and assorted Python tools are as mature as the language.
- Python is an ideal language for your business logic. It is easy to learn, eminently readable and generally immune to programming gotchas.
Patches, comments and other help is greatly appreciated. If you need help, post to the SourceForge mailing list or forums. Please include code snippets for the most accurate response.
<<lessMain features:
- Using the native Python interpreter may mean a massive speed improvement over Java-based languages.
- Python is mature so authors neednt fear the interpreter will suddenly change widely-used features.
- Access to the high quality Python modules, both native and Python-based.
- Compilers and assorted Python tools are as mature as the language.
- Python is an ideal language for your business logic. It is easy to learn, eminently readable and generally immune to programming gotchas.
Patches, comments and other help is greatly appreciated. If you need help, post to the SourceForge mailing list or forums. Please include code snippets for the most accurate response.
Download (0.60MB)
Added: 2007-03-17 License: GPL (GNU General Public License) Price:
956 downloads
Java Web Shell 0.0.8
Java Web Shell is a web based interactive shell-type environment written in Java. more>>
Java Web Shell is a web based interactive shell-type environment written in Java.
Obviously, to use the shell, youll need to be using a browser that supports Java Applets, and this has been compiled using the Sun 1.4.1 JDK.
Head over to Sun and pick up the latest runtime enviroment if you dont already have it.
<<lessObviously, to use the shell, youll need to be using a browser that supports Java Applets, and this has been compiled using the Sun 1.4.1 JDK.
Head over to Sun and pick up the latest runtime enviroment if you dont already have it.
Download (0.013MB)
Added: 2007-03-12 License: GPL (GNU General Public License) Price:
968 downloads
Java Tools 0.30
Java Tools is a lightweight integrated development environment for creating, compiling, and executing Java applications. more>>
Java Tools is a lightweight integrated development environment for creating, compiling, and executing Java applications and applets.
Java Tools includes point and click access to the Java files, commands, and documents. It also includes a built-in text editor and user interface for the Java debugger.
It is intended for the new Java user who needs help getting started. Its also for the more experienced Java user who wants easy access to the Java commands and a text editor.
Main features:
- GUI with built-in help and small footprint.
- Point and click access to all files (Java, manifest, HTML, image and sound) and directories (package).
- Point and click access to all commands for compiling (javac), archiving (jar), documenting (javadoc), executing (java), debugging (jdb) and disassembling (javap).
- Point and click access to all documents (Java API Specification, Java Tools and Utilities, Java Features and Java Tutorial).
- Point and click creation of all files (Java, manifest and HTML) and directories (package).
- Point and click installation of distribution archive files (Java document, Java source code, Java Tutorial and Sun Tools).
- Automatic determination of class file dependencies for archiving (jar) and documenting (javadoc) Java files.
- Checking for unused, redundant and missing imports.
- Logging of all commands invoked by GUI.
- Code metrics for Java files.
- Built-in text editor (see Edit for details).
- Built-in user interface for the Java debugger with command-line editing and history.
- Self-installing executable (Java archive file).
- Comprehensive installation and user documentation for Java and Java Tools.
<<lessJava Tools includes point and click access to the Java files, commands, and documents. It also includes a built-in text editor and user interface for the Java debugger.
It is intended for the new Java user who needs help getting started. Its also for the more experienced Java user who wants easy access to the Java commands and a text editor.
Main features:
- GUI with built-in help and small footprint.
- Point and click access to all files (Java, manifest, HTML, image and sound) and directories (package).
- Point and click access to all commands for compiling (javac), archiving (jar), documenting (javadoc), executing (java), debugging (jdb) and disassembling (javap).
- Point and click access to all documents (Java API Specification, Java Tools and Utilities, Java Features and Java Tutorial).
- Point and click creation of all files (Java, manifest and HTML) and directories (package).
- Point and click installation of distribution archive files (Java document, Java source code, Java Tutorial and Sun Tools).
- Automatic determination of class file dependencies for archiving (jar) and documenting (javadoc) Java files.
- Checking for unused, redundant and missing imports.
- Logging of all commands invoked by GUI.
- Code metrics for Java files.
- Built-in text editor (see Edit for details).
- Built-in user interface for the Java debugger with command-line editing and history.
- Self-installing executable (Java archive file).
- Comprehensive installation and user documentation for Java and Java Tools.
Download (0.15MB)
Added: 2007-07-09 License: Freeware Price:
838 downloads
VietIME 1.3
VietIME is a Java-based Vietnamese input method editor (IME). more>>
VietIME is a Java-based Vietnamese input method editor (IME). Enable input of Vietnamese Unicode text in Javas AWT and Swing text components.
VietIME uses the input method framework in the Java 2 platform (1.3 or higher) to enable the collaboration between text editing components and input methods in entering Vietnamese text with any Java runtime environment.
Text editing components that use the input method framework run on any Java application environment and support any text input methods available on that Java application environment without modifying or recompiling the text editing component.
Main features:
- Multi-platform
Windows
Solaris
Linux/Unix
Mac OS X
Others
- Unicode compatibility
- Common Vietnamese input methods
VNI
VIQR
Telex
- SmartMark
- Spell Check, Convert, Change Case, Strip/Normalize Diacritics, Sort Vietnamese words, etc. (available only to Swing applications)
<<lessVietIME uses the input method framework in the Java 2 platform (1.3 or higher) to enable the collaboration between text editing components and input methods in entering Vietnamese text with any Java runtime environment.
Text editing components that use the input method framework run on any Java application environment and support any text input methods available on that Java application environment without modifying or recompiling the text editing component.
Main features:
- Multi-platform
Windows
Solaris
Linux/Unix
Mac OS X
Others
- Unicode compatibility
- Common Vietnamese input methods
VNI
VIQR
Telex
- SmartMark
- Spell Check, Convert, Change Case, Strip/Normalize Diacritics, Sort Vietnamese words, etc. (available only to Swing applications)
Download (0.13MB)
Added: 2007-07-13 License: GPL (GNU General Public License) Price:
998 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above java runtime environment search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed