Wicket is a Java Web application framework implementing simplicity, separation of concerns, and ease of development. Wicket pages can be mocked up, previewed, and later revised using standard WYSIWYG HTML design tools. Dynamic content processing and form handling is all handled in Java code using a component model backed by POJO data beans that can easily be persisted using your favourite technology.
Wicket Web Beans (WWB) is an Apache Wicket component toolkit for displaying and editing POJOs that conform to the JavaBeans specification. Web pages are automatically generated based on bean properties and certain conventions. If necessary, the layout, editability, and actions of these pages can be customized on an exception basis. In other words, the toolkit normally does what you'd expect, but when it doesn't, you can override its behavior.
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.
Wiseman is an implementation of the WS-Management specification for the Java SE platform. The project scope includes the WS-Management specification and its dependent specifications, which can be found at http://www.dmtf.org/standards/wbem/wsman/. The project requires Java SE 5+ or above, and is built on JAXB 2.0 and SAAJ 1.3 (part of the JAX-WS project). Ant scripts for standalone and Netbeans builds are supplied.
XMLImportDB provides an easy-to-use interface that allows developers to create a baseline database environment that can be embedded in their source code for use in jUnit test cases. The database environment can be described in a separate file in the same package as the tests, in a hard coded string in the test case classes, or in any other location for which a java.io.Reader can be created at runtime.