Batik is a Java-based toolkit for applications that want to use images in the Scalable Vector Graphics (SVG) format for various purposes, such as viewing, generation, or manipulation. It gives developers a set of core modules (parsers, generators, DOM implementation) which can be used together or individually, and be highly extensible. It comes with a full-fledged SVG viewer.
BeanKeeper is a full featured, powerful object/relational persistence and query library. It has a unique philosophy of simpleness and ease of use: it does not require config files, annotations, code generation, code "enhancing", or any kind of tools to be used. It handles simple Java beans (or POJOs) and its query service returns lists. Despite its simpleness, under the hood the library takes care of all the necessary logic: transaction visibility, result list paging, keys and ids, table creation/modification, class relations, inheritance/polymorphism, case sensitiveness, and much more. It currently supports: Oracle, HSQLDB, MySQL, and PostgreSQL.
BeanView is a Java library for rendering a JavaBean to a user interface form. It supports both Swing and Echo 2 (an Ajax web framework). Simply create a BeanView panel, set a JavaBean instance, and the form is instantly created. You can update the JavaBean from the form and back with a single line. It uses reflection and (optional) annotations to determine the default form labels, fields, and widgets, with support for validation-via-annotations.
Beanlet is an IoC container that was inspired by EJB3 and Spring. Beanlet's programming model looks similar to that of EJB3, but offers much of the flexibility of Spring. The Beanlet architecture supports JTA transactions, JMX, the Java Persistence API, Web integration, and the Spring Framework. It is meant for software projects that only require a subset of the features of a full blown EJB server. Beanlet brings many of the features of EJB to the world of the Java Standard Edition without the restrictions and limitations of EJB.
Berkeley DB Java Edition is a high performance transactional storage engine written entirely in Java. Like the highly successful Berkeley DB product, it executes in the address space of the application without the overhead of client/server communication. It stores data in the application's native format, so no runtime data translation is required. It supports full ACID transactions and recovery, and provides an easy-to-use interface, allowing programmers to store and retrieve information quickly, simply, and reliably.
Berkeley DB XML is a native XML database engine for use within your product. Made available as a C++ library with language bindings for Java, Perl, Python, PHP, and Tcl, it integrates directly into your application (it is not a standalone database server). It provides XQuery access into a database of document containers. XML documents are stored and indexed in their native format using Berkeley DB as the transactional database engine.
The Beryl XML GUI library was written to ease the development of graphical user interfaces using Swing on Java. It lets you store user interfaces as XML markup. This will help you avoid unnecessary clutter in your source; Swing code mixed with application logic can become a troublesome and hard-to-read mess as the application size increases. The library comes with a visual component builder, which makes development easy.