Free j2se software for mac

JCCKit is a free and open source library and a very flexible framework for creating scientific charts and plots.
NOTE: JCCKit is licensed and distributed under the terms of the GNU Library or Lesser General Public License (LGPL).

Main features:
- small (< 100Kb jar file)
- highly configurable due to a sophisticated configuration concept
- extensible (1/3 of all classes are interfaces or abstract classes.)
- automatic updating if data changes
- easy programming of dynamic charts and plots
- automatic rescaling if canvas size changes
- out-of-the-box applet for presenting static data on a web page without needing knowledge of the Java programming language.
- automatically generates a legend
supports:
- logarithmic axes
- non-numerical tic labels
- different line styles, colors, and thicknesses
- different symbols
- different fonts, font styles, colors, and text orientations
- vertical and horizontal error bars
- vertical, horizontal, and stacked bar charts
supported devices:
- AWT Graphics context
- AWT Graphics2D context (needs Java 2 platform)
- Off-Screen image creation (need J2SE 1.4 or higher) (see section 2.5 of the User Guide)
- SVG (Scalable Vector Graphics)

System requirements:
-

Enhancements
Features:
- Double-buffering can be switched off to allow off-screen image creation.
Documentation:
- double-buffering can be switched off
- new configuration manual

ESXX, pronounced Essex, is a web application server that executes web applications written in JavaScript (a.k.a. ECMAscript) on the server-side.
Its written in Java and has no external dependencies except for J2SE 6.0, everything else thats required is packaged in one single, executable JAR file, ready to be tested in Mac OS X,Linux, Solaris, Windows or any other platform where Java 6

Main features:
- JavaScript 1.7, provided by Rhino. Modern JavaScript really is a fantastic language. Well be tracking Rhino releases, so expect 1.8 and 2.0 in the future.
- E4X extensions, meaning unparallelled ease of use when working with XML documents.
- XSLT 2.0, provided by Saxon 9, for state-of-the-art XML transformations with access to user-defined JavaScript and Java extension functions directly from the XSLT templates.
- Embedded SQL database (H2), for quick prototyping or situations where a non-distributed web application is simply good enough.
- Built-in web server, suitable for development and small-scale deployments.
- Secure by default: ESXX is designed to make the applications immune to SQL injection or XSS attacks.
- Encourages layer separation and state-less design, resulting in highly scalable, easily maintainable web applications.
- Ready for the multi-core era: supports multithreaded JavaScript applications with easy-to-use fork/join and parallel array primitives.
- A RESTful mindset that encourages good-looking URIs and exposes web services/resources, local files, LDAP directories and SQL databases using the same API.
- Full access to J2SE 6: Thats thousands of useful classes and arguably one of the best runtime environments on the planet. Naturally, you can plug in your own or 3rd party Java code too, as well as native JNI modules.
- Standards-based: JavaScript, XML, XSLT, SQL, Java. This is stuff you probably already know, so youll be productive in no time.

Enhancements
- Added the XKCD example from the Wiki.
- Fixed apps in examples to use req.scriptURI instead of the web-server dependent CGI variable SCRIPT_NAME.
- Added DOCUMENT_ROOT CGI variable in HTTP mode.
- Added Java EE Servlet support: ESXX can now run inside a J2EE application server, such as Glassfish or Tomcat.
- XSLT parameters may now be specified via the property params in the ESXX.Response object.
- A build.xml file is now included in esxx.war, so it can easily be rebuilt with custom content.
- Added esxx.host, which refers to a host object that can be set when ESXX is embedded. For instance, If ESXX is deployed as a Servlet, esxx.host will refer to that Servlet.
- Added HTTP filter support. And there was much rejoicing.
- Property requestMethod is now available on the ESXX.Request object.
- Upgraded to Rhino 1.7 release 2 + patch for bug #477233.
- Added command line option --db-console to start H2s database console.
- Added the "Hello world" and "The Ajax Blog" tutorials to the examples.
- All-new look of error messages and file listings. No more references to esxx.org resources, everything is now embedded.
- Updated to Saxon 9.0.0.8.
- Added an uninstall script for OSX.
- Removed utility file esxx/Object.js. Use Function.bind() from esxx/harmony.js instead of Object.$(). Hey, its still alpha!
- Well, actually its not. Hello, beta!

The Eclipse Project is an open source software development project dedicated to providing a robust, full-featured, commercial-quality, industry platform for the development of highly integrated tools.
The mission of the Eclipse Project is to adapt and evolve the eclipse technology to meet the needs of the eclipse tool building community and its users, so that the vision of eclipse as an industry platform is realized.
Eclipse is a kind of universal tool platform - an open extensible IDE for anything and yet nothing in particular.
The real value comes from tool plug-ins that "teach" Eclipse how to work with things - java files, web content, graphics, video - almost anything one can imagine. Eclipse allows tool builders to independently develop tools that integrate with other peoples tools so seamlessly you cant tell where one tool ends and another starts.
Main features:
Workbench
- The term Workbench refers to the desktop development environment. The Workbench aims to achieve seamless tool integration and controlled openness by providing a common paradigm for the creation, management, and navigation of workspace resources.
- Each Workbench window contains one or more perspectives. Perspectives contain views and editors and control what appears in certain menus and tool bars. More than one Workbench window can exist on the desktop at any given time.
Java development
- The JDT project provides the tool plug-ins that implement a Java IDE supporting the development of any Java application, including Eclipse plug-ins. - It adds a Java project nature and Java perspective to the Eclipse Workbench as well as a number of views, editors, wizards, builders, and code merging and refactoring tools. The JDT project allows Eclipse to be a development environment for itself.
Team programming with CVS
- In the Concurrent Versions System (CVS) team programming environment, team members do all of their work in their own Workbenches, isolated from others. Eventually they will want to share their work. They do this via a CVS Repository.
Branches
- CVS uses a branch model to support multiple courses of work that are somewhat isolated from each other but still highly interdependent. Branches are where a development team shares and integrates ongoing work. A branch can be thought of as a shared workspace that is updated by team members as they make changes to the project.
- This model allows individuals to work on a CVS team project, share their work with others as changes are made, and access the work of others as the project evolves. A special branch, referred to as HEAD, represents the main course of work in the repository (HEAD is often referred to as the trunk).
Sharing work
- As team members produce new work, they share this work by committing those changes to the branch. Similarly, when they wish to get the latest available work, they update their local workspaces to the changes on the branch.
- Thus the branch is constantly changing, moving forward as team members submit new work.
- The branch effectively represents the current state of the project. At any point a team member can update their workspaces from the branch and know they are up to date.
Plug-in Development Environment
- The Plug-in Development Environment (PDE) provides a rich set of tools to create, develop, test, debug and deploy Eclipse plug-ins, fragments, features, update sites and RCP products. PDE also provides comprehensive OSGi tooling, which makes it an ideal environment for component programming, not just Eclipse plug-in development.

System requirements:
- Apple Java 2 Platform Standard Edition (J2SE) 5, service release 4 for Tiger

Enhancements
- New update UI - The UI for performing installation and updates is completely new in 3.4. The new UI is accessed using Help > Software Updates.
- Viewing available software - You can now view the software thats available for install or update in multiple ways. The Available Software tab in the Help > Software Updates dialog provides a view menu button that lets you view the software by site, category, or name.
- Markers view - A new Markers view has been added for users who prefer to have their problems, bookmarks and tasks in the same view (i.e., as it was back in the days before Eclipse 3.0). It can be found by selecting Window > Show View > Other > Markers.
- New look for Problems, Bookmarks and Tasks views - The Problems, Bookmarks and Tasks views now have a new look, implementing many long-standing feature requests.
- Many more improvements and changes

Tomcat is the servlet container that is used in the official Reference Implementation for the Java Servlet and JavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications are developed by Sun under the Java Community Process.
Tomcat is developed in an open and participatory environment and released under the Apache Software License. Tomcat is intended to be a collaboration of the best-of-breed developers from around the world.
Enhancements:
- Tomcat 5.5 is designed to run on J2SE 5.0 and later, and requires configuration to run on J2SE 1.4. Make sure to read the RUNNING.txt file in the fulldocs downloadable file(s) if you are using J2SE 1.4.
- In addition, Tomcat 5.5 uses the Eclipse JDT Java compiler for compiling JSP pages. This means you no longer need to have the complete Java Development Kit (JDK) to run Tomcat, but a Java Runtime Environment (JRE) is sufficient. The Eclipse JDT Java compiler is bundled with the binary Tomcat distributions. Tomcat can also be configured to use the compiler from the JDK to compile JSPs, or any other Java compiler supported by Apache Ant.