The deepOfix Mail Server makes it possible for organizations with minimal technical expertise to have robust server infrastructure. deepOfix offers unprecented ease of use, doesn't require prior GNU/Linux experience and is backed by a full-time development and support team. deepOfix features LDAP-based directory services for user account management, email delivery, distribution lists, and addressbooks. It also includes built in tools for spam and virus control, webmail, and fetching email.
Jat (Java Application Template) is a Java framework that is easy to extend. It supplies modular and flexible basic functionalities to develop Web and standalone applications. It can improve application start-up time. Jat Portal is an enhanced version of Jat. It provides several pre-configured features to build a complete Web application.
The goal of dzo is to treat application database objects the same way the application's source code is treated, with respect to development, revision control, and deployment. Dzo uses a text file that contains native create statements for all database objects and compares them against the actual database-schema. As a result, dzo creates the SQL statements needed to update the database schema (or you can let dzo execute the SQL statements directly). If your application lives in a Tomcat or Java EE application server, dzo has a servlet that controls the deployment process, inspects and executes the necessary database changes, and finally deploys the application. Dzo currently works with HSQLDB, MySQL, Oracle, PostgreSQL, and SQL Server (more to come).
Sight is a Java Web framework built on top of J2EE technologies, and particularly on top of the servlet API. SightWF provides a simple programming model for building RIA applications. SightWF is initially designed to be deployed on Google App Engine, and can be run in a J2EE servlet container such as Tomcat.
Perfmon4j is a suite of performance monitoring tools that are intended to be used to diagnose performance bottlenecks and monitor throughput and response time in production Java applications. Its main features include servlet response time monitoring, detailed thread trace sampling, Java instrumentation that enables Package, Class, and Method monitoring without code modification, snapshot monitoring of system metrics including Garbage Collection, Memory Pools, etc., an API for applying additional monitoring points via method annotations or in-line timers, and support for dynamically enabling monitors in running applications.
SlimWeb aims to replace Struts or JSF in your J2EE application, but is closer to Rails or TurboGears in its heavy use of convention-over-configuration, simplicity, and power. It aims to reduce (and most of the time completely eliminate) all boilerplate code, XML configuration files, and even deployment times.
With the Cibet framework, it is very easy to add various control mechanisms into a JPA and/or EJB-based Java application. The actual version includes control schemes like Archiving (manipulation of domain objects; data and execution of business processes are archived). From the archived state, domain objects can be reconstructed and business processes can be re-invoked with the same parameters at any time. The archive entries are secured against manipulation to make them audit-proof and revision safe. Four-eyes principle: this scheme is an example of a dual control mechanism: A user wants to perform some critical data manipulation or business process. With an applied dual control mechanism, the action is not executed in the production system directly, but stored and postponed. A second user must check the data and the action and can approve or decline. Only when the second user approves, the data manipulation or business process is executed in the production system; otherwise it is discarded. An even stricter example for a dual control mechanism is the six-eyes principle. In this case, a third user must approve a data manipulation or business process before it will become productive.