QueryForm is a Java GUI application that provides a powerful form-based front end for relational databases. It supports multiple concurrent connections to different databases. Tables can be queried through a simple form-based interface or a custom WHERE-clause editor. Query results can be browsed one row at a time through the the form interface or viewed in a scrollable grid, and can be exported to CSV files or INSERT statements. Table rows can be created, updated, or deleted, and table metadata can be viewed for each table in a database.
FormProc is an open source Java library designed to make handling and validating forms (including Web forms) easy. Forms are represented as objects which manage a collection of form elements. Submitted data can be validated through several mechanisms including regular expressions, BSF-supported scripting languages, and custom Java classes.
rpaf changes the remote address of the client on incoming proxy requests. It is used in backend servers that needs to know the IP of the client, and works in conjunction with mod_proxy_add_forward (which sets the X-Forwarded-For header). When an X-Host header exists rpaf will take the hostname found here, put it into Apache, and update the virtualhost settings so that you can serve virtualhosts on the backend. It includes modules for both Apache 1.3 and 2.0.
Enterprise Object Broker (EOB) is an application server that transparently distributes Java objects via their interfaces. It makes no distinction between Local and Remote objects. Because of these features, it is not J2EE compliant. The developer builds beans that implement normal Java interfaces and the deployer decides where the beans are in a cluster of servers. Apache's AltRMI is used in place of RMI. It publishes plain interfaces locally and remotely. The interfaces do not have to extend the java.rmi.Remote interface. Methods do not have to throw RemoteException. AltRMI delivers remoting for Java. EOB sits on top of Apache's Avalon-Phoenix server platform.
The Jakarta Commons HTTP Client component supports the client-side of RFC 1945 (HTTP/1.0) and RFC 2616 (HTTP/1.1), several related specifications (RFC 2109 (Cookies), RFC 2617 (HTTP Authentication), etc.), and provides a framework by which new request types (methods) or HTTP extensions can be easily created.