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.
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.
Butterfly Web UI is a component based Java Web application framework. Like the rest of the Butterfly Components, Butterfly Web UI is extremely small and very flexible. Butterfly Web UI uses Butterfly Container internally, a state of the art dependency injection container. Using Butterfly Web UI, it is easy both to generate HTML for a Web browser or XML or JSON for a RIA frontend (Flex, JavaFX, Silverlight) or AJAX frontend. You also can easily create HTML layout templates that are reused throughout your Web application, so you don't have the layout hardcoded into every page. You can easily mix RIA and non-RIA Web application technology in the same Web application.
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.