Free how to open java class file software for linux

Open Java Console is an extension which provides the ability to open the Java Console in Firefox.

This extension provides an option on the Tools menu that opens the Java Console, and a toolbar button in the JavaScript Console that also allows the console to be opened. The extension also adds the keystroke Ctrl+Shift+J to spawn the console from the keyboard, from either a browser window or the JavaScript Console.

New features in 1.0 include the addition of two preferences:

A preference for logging a message to the JavaScript Console whenever the Java Console is triggered

A preference for showing any exceptions generated by the browser when starting the Java Console

Mozilla 1.X has this feature, but Firefox does not, making access to the console difficult unless this extension is used.

When the Console^2 extension is installed, the Ctrl+Shift+J keystroke will trigger the Error Console instead of the Java Console from a browser window. Ctrl+Shift+J will still work from the Error Console.

The following languages have been added to the 1.6 release: Hungarian and Dutch.

The Kiwi Toolkit project is a foundation class library containing many useful classes that complement the Java Foundation Classes (JFC).
It includes many classes and components that were not provided with the JFC, such as a TreeTable component, a DateChooser, an MVC charting package (bar charts, line charts, pie charts), a plugin framework for Java, an application resource manager (for loading images, icons, HTML pages, audio clips, and other resources from JAR files), a better internationalization API, and much more.
Enhancements:
- This release adds some new classes and includes various bugfixes.

Test::Unit::InnerClass is a unit testing framework helper class.

SYNOPSIS

This class is not intended to be used directly

This class is used by the framework to emulate the anonymous inner classes feature of Java. It is much easier to port Java to Perl using this class.

Construct is a framework for command processing. It is based on a request/response cycle managed by a Controller. Construct-java has support for filters, filter chains and command chaining. The controller has two modes for request processing: synchronous and asynchronous. Validators (commons-validator) are also supported.
Main features:
- Synchronous/Asynchronous request procesing
- Command chaining (Chain of Responsability)
- Apply filters before and after request processing
- Commons-validator support
- Spring integration
Enhancements:
- Open source release to java.net.

The Asterisk-Java package consists of a set of Java classes that allow you to easily build Java applications that interact with an Asterisk PBX Server. Asterisk-java supports both interfaces that Asterisk provides for this scenario, The FastAGI protocol and the Manager API.
Asterisk-Java is compatible with Asterisk 1.0 and 1.2. The FastAGI implementation supports all commands currently available from Asterisk.
The Manager API implementation supports receiving events from the Asterisk server (e.g. call progess, registered peers, channel state) and sending actions to Asterisk (e.g. originate call, agent login/logoff, start/stop voice recording).
Enhancements:
- This release has full support for Asterisk 1.4 and the new Live API (org.asteriskjava.live).
- The Live API takes care of the low-level action and event handling of the Manager API, and offers an intuitive API for Java developers.
- Asterisk-Java takes advantage of the features of Java 5.0, and therefore requires a Java Virtual Machine of at least version 1.5.0.

BioJava is an open-source project dedicated to providing a Java framework for processing biological data. It include objects for manipulating sequences, file parsers, DAS client and server suport, access to BioSQL and Ensembl databases, and powerful analysis and statistical routines including a dynamic programming toolkit.

Template::Plugin::Java is a Perl module that can generate Java Classes from XML description files and templates.

SYNOPSIS

From an xml file such as:
< aBean >
< java: option1="value1" >
< option2 >value2< /option2 >
< /java: >
< foo >10< /foo >
< bar >String< /bar >
< container >
< baz >20< /baz >
< /container >
< /aBean >

Through the program "tjava":

tjava [options] [file.xml ...]

Via a template, such as:

[% USE Java %]
package $package;

public class $class {

[% FOREACH Java.variables %]
$type $name = $initializer;
[% END %]

//... etc
}

To generated Java source code in the appropriate directory as determined by the package of the .xml files directory, specified package option if any, and CLASSPATH.

OPTIONS

Any options may be given besides those listed, these are passed directly to the Templates being processed in the stash (the variable table at time of processing). They can be given in the < java: > ... < /java: > section of an XML file (in which case, dont use the -- dashes) as attributes or elements, or on the command line.

--template

Name of the template to process. No extension is assumed by default unlike in the previous version.

--package

Destination package to put the generated classes, otherwise will be determined from how the current directory relates to the CLASSPATH.

--class

Class name to use, otherwise will infer from the root tag of the XML file.

--templatePath

Colon separated path where the templates can be found, overrides the environment variable TEMPLATEPATH. This doesnt work right now, so use the TEMPLATEPATH environment variable.

--genContainers

If set to 0, classes for subcontainers will not be generated. This is generally not useful.

--containerTemplate

By default set to Container, this is the default template, as well as the template used for sub-containers.

--containerNamePrefix

By default, if generating class Foo that needs to have a sub container wrapped in tag < bar >, its name will be FooBar. This is safe and wont cause collisions with different classes having sub containers of the same name (until some sort of dependency checking code is introduced). To turn this off, set it to the empty string "".

--interface

Interface to add to list of implemented interfaces, can be supplied multiple times. Make sure you append any necessary code to implement any of these interfaces.

--append

Text to insert in the generated class body.

--appendFile

Will insert text read from the file specified into the generated class body. This option and the --append option are mutually exclusive.

--file[s]

The XML file(s) to parse. This is useful for when the Plugin is instantiated from a custom script, not via tjava or inside a template.

Any other option will be placed into the stash for the templates to use, making tjava very useful with your custom templates.

Anything thats not an option will be assumed to be a file.