WidgetServer is a Java/XML server-side GUI-framework which enables an application to run as either a monolithic Swing app, a client/server Swing app, or as a Web app without any change and without loss of functionality. An Eclipse Plugin is available as well. A rich widget set is supported that includes tree views, tabbed panes, split panels, and much more. Animations, all types of events, and several effects are supported, as well. A unified widget-based, object-oriented programming interface for Web and Swing GUIs is offered to the developer to control and assemble the GUI. Web applications are fully AJAX enabled. For Swing client/server applications, the framework handles client/server communication, including compression and security layers.
Poor Man's Imaging Wrapper a clean and simple API wrapper over JAI, Java2D, ImageIO, and AWT. It supports a set of imaging operations (read, write, scale/resize, crop, grayscale, add transparency, rotate, add border, flip/mirror, add text, overlay, blur, sharpen, etc.) with simple direct calls to the API. If you want to switch from Java2D to JAI, all you need to do is add JAI jars to the classpath. It supports GIF encoding if PJA tools jars are available in the classpath.
Conary is a distributed software management system for Linux distributions. It replaces traditional package management solutions (such as RPM and dpkg) with one designed to enable loose collaboration across the Internet. It enables sets of distributed and loosely connected repositories to define the components which are installed on a Linux system. Rather than having a full distribution come from a single vendor, it allows administrators and developers to branch a distribution, keeping the pieces which fit their environment while grabbing components from other repositories across the Internet.
Studs MVC Framework+ contains a port of Apache's Jakarta Struts to PHP, though the libraries included in the rest of the project are much more vast. In order to implement the Struts port, it was necessary to build a core, object-oriented API in the style of the JDK and the Jakarta Commons, a servlet container to handle HTTP requests and to invoke servlet classes, and finally, a parsing engine for JSP-style template pages. In the end, the result is an environment which is very similar to that provided by a J2EE Web Container, only everything is implemented in PHP. While it was possible to carry over many of the concepts, designs and mechanisms from J2EE, some limitations do exist due to the nature of the PHP programming language, such as the lack of checked exceptions (runtime only).