AuthenticRoast allows you to build highly flexible authentication mechanisms for the Java Web tier. This can be anything from HTTP Basic authentication to authenticating with openid, facebook, or your company's Kerberos setup. The authentication modules can be combined at will and even changed at runtime. This currently works for glassfish and plain Tomcat, and allows you to use all the features of container-managed security without being constrained to the simple login methods provided.
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).
Spring ME is a version of ME that not only runs on your cell phone, but also on any other Java platform not supporting reflection. It is to Java ME what Spring is to Java SE and Java EE, which is indicated by the name. However, the "ME" (Micro Edition) suffix not only refers to the platform it supports. It also refers to the size of the runtime, which is pretty minimal. In fact, it's pretty much non-existent, and therefore ideal for situations in which you cannot afford the sheer size of the traditional Spring runtime.
AppDynamics an application performance management solution for mission-critical Java applications. It can organize user requests and business transactions, monitor business transaction health, identify and diagnose slow requests, identify and diagnose errors, and drill down. It is built from the ground up for highly distributed service-oriented environments. It has fast root cause diagnostics at the method/class level, but creates no more than 2% overhead, even in high-volume production deployments. It can not only manage applications, but dynamically scale them in cloud and virtual environments.
The Imixs Workflow project offers a Java based BPM framework to build workflow management systems (WFMS) in a fast and easy way. The project provides different components and sub-projects that contribute to the development of workflow solutions in any kind of Java or Java EE application. The goal of this project is to offer an easy-to-use Java based technology with a focus on human based workflow. This means that the Imixs Workflow is typically applied to human-to-human workflow applications. But it can also be used for technical business process management solutions (BPM). The Imixs JEE Workflow is a full featured Workflow Management System (WFMS) based on the JEE specification. The project extends the Imixs Workflow API project to fulfill the requirements to a scalable, transactional, robust and simple deployable Java EE Workflow System. The Project provides different service components (EJBs) to be used in any kind of BPM application.