Flaka is an extension for Ant that runs with Ant versions 1.7.x and 1.8.x. A main project goal of Flaka is the simplification of writing a build script. It requires Ant >= 1.7.x and Java >= 1.5. It provides an expression language (Java Unified Expression Language) allowing access to data objects that makes many scripting parts in Ant scripts unnecessary. It provides conditional and repetitive control structures like when, unless, while, for, choose, switch, etc. It provides exception handling. It provides additional types, tasks, and macros. It provides comprehensive documentation.
GWiki is an embeddable Wiki engine. It allows users to edit rich text fragments in an application you develop. It supports I18N files and mulitimedia content. Gwiki can be extended with macros written in Java or Groovy. It has a powerful right and role system, which can be fed from external sources such as LDAP, and allows access to business entitiels from wiki pages. It comes with Wicket integration out-of-the-box. Wicket-HTML-Fragments can be held within GWiki, so these pages can be managed by the Wiki System, while Wicket handles the application logic. GWiki can be deployed as a servlet on every servlet container. GWiki can use a filesystem, a Zip archive, or a database for its content storage.
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.
BRAP is a Java remoting protocol that uses native Java object serialization encapsulated in HTTP. It aims to be an alternative to Spring HttpInvoker and Spring Security, especially when you don't need or want the dependencies of Spring in your client, such as when building a rich client application where size might be an issue. The authentication mechanism lets you use your own domain objects as credentials. BRAP gives you "pass by reference" even though the object arguments are serialized and passed to the remote service: changes that happen on the remote side can be applied to the client side automatically. BRAP focuses on being easy to use, small in size, yet powerful and extensible.