Ports Search

Apache TomEE is an all-Apache Java EE 6 Web Profile certified stack where Apache Tomcat is top dog. Apache TomEE is assembled from a vanilla Apache Tomcat zip file.

Armed Bear The right of the people to keep and arm bears shall not be infringed! Armed Bear Common Lisp (ABCL) is an implementation of ANSI Common Lisp that runs in a Java virtual machine. It provides a runtime system, a compiler that compiles Lisp source to JVM bytecode, and an interactive REPL for program development. ABCL runs on platforms that support Java 1.5 (or later), including Linux, Windows, and Mac OS X.

Saxon is a collection of tools for processing XML documents. The main components are: - An XSLT 2.0 processor, that can be used from the command line, or invoked from a Java application by use of the standard JAXP API. Saxon can be integrated with Java applications using the JAXP API, which means it is possible for a Java application to switch between different XSLT processors without changing the application code. As well as conforming closely with the XSLT 2.0 specification, Saxon offers a number of powerful extensions. - An XPath 2.0 processor accessible via an API to Java applications. - An XQuery 1.0 processor that can be used from the command line, or invoked from a Java application by use of an API. - An XML Schema 1.0 processor. This can be used on its own to validate a schema for correctness, or to validate a source document against the definitions in a schema. It is also used to support the schema-aware functionality of the XSLT and XQuery processors. So you can use Saxon to process XML by writing XSLT stylesheets, by writing XQuery queries, by writing Java applications, or by combinations of the approaches.

The Saxon-B 9.1 package is a collection of tools for processing XML documents. The main components are: - An XSLT 2.0 processor, that can be used from the command line, or invoked from a Java application by use of the standard JAXP API. Saxon can be integrated with Java applications using the JAXP API, which means it is possible for a Java application to switch between different XSLT processors without changing the application code. As well as conforming closely with the XSLT 2.0 specification, Saxon offers a number of powerful extensions. - An XPath 2.0 processor accessible via an API to Java applications. - An XQuery 1.0 processor that can be used from the command line, or invoked from a Java application by use of an API. - An XML Schema 1.0 processor. This can be used on its own to validate a schema for correctness, or to validate a source document against the definitions in a schema. It is also used to support the schema-aware functionality of the XSLT and XQuery processors. So you can use Saxon to process XML by writing XSLT stylesheets, by writing XQuery queries, by writing Java applications, or by combinations of the approaches.

This library reads song information, such as song title, artist, and album, from an MP3 file. It supports ID3v1, ID3v1.1, Lyrics3v1, Lyrics3v2, ID3v2.2, ID3v2.3, and ID3v2.4 tags. MP3 Frame Headers can also be read. There is a FilenameTag, a ID3v2.4 tag that is intelligently derived from the file name. It contains tag synchronization utilities, multiple save options, and easy tag conversion methods.

Jaxup defines an interface to update XML documents, through which clients can work without knowledge of the exact object model that the document uses. The interface is called Updater, and the idea behind it is the same as with Jaxen's Navigator interface. In addition, an implementation of xmldb.org's proposed XUpdate specification is provided. The implementation is in the XUpdate class. Implementations of the Updater interface are provided for the following object models: - DOM - Dom4j - JDom

YAAC is a platform-independent Java application for monitoring and contributing to the Automatic Packet Reporting System (APRS) network.

jclassinfo reads java class files and provides information about the class, dependencies and more. It is a pure C implementation.

Provide a standard and simplified way to build and package Ruby extensions (C, Java) using Rake as glue.

The HttpCore components implement the most fundamental aspects of the HTTP protocol. They are nonetheless sufficient to develop basic client-side and server-side HTTP services with a minimal footprint and no external dependencies. The HttpCore base module contains the public API and the default implementation based on the Java classic (blocking) I/O model. It requires a Java 1.3 compatible runtime and has no dependency on any external libraries. HttpCore NIO extensions contain optional components that leverage the event driven, non-blocking I/O (NIO) model. HttpCore NIO extensions require a Java 5.0 compatible runtime and the HttpCore base module. HttpCore NIO extensions are intended for those usage scenarios where raw throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner.