Azzyzt JEE Tools is a set of Eclipse plugins for creating a so-called "azzyzted" project, and for creating code from a model. Azzyzt uses Java JPA entities as a model, and from that model it creates an enterprise application, ready to be deployed in a Java EE 6 application server like GlassFish 3.1, ready to be accessed via CORBA, SOAP, and REST. Thus the generated application is a set of Web services, providing all that you need in a typical CRUD application. Generated enterprise applications have separate source folders for generated and developer-supplied content. You can add your own functionality to a well-engineered base project. Azzyzt JEE Tools is not about user interfaces. It is expected that the generated application is accessed by a RIA frontend or by a fat client.
Citrus is a test framework written in Java that enables automated integration testing of message-based enterprise SOA applications. The tool can easily simulate surrounding systems across various transports and protocols (e.g. JMS, SOAP WebServices, HTTP, TCP/IP, etc.) in order to perform end-to-end use case testing. Citrus provides strong validation mechanisms for XML message contents and allows you to build complex testing logic such as sending and receiving messages, database validation, automatic retries, variable definitions, dynamic message contents, error simulation, and many more.
LemonLDAP::NG is a modular Web SSO based on Apache::Session modules. It simplifies the building of a protected area with a few changes in the application. It manages both authentication and authorization and provides headers for accounting, so you can have full AAA protection for your Web space. LemonLDAP::NG is a complete rewrite of LemonLDAP. All components needed to use it and to administer it are included in the tarball. However, all modules developed for LemonLDAP may not work with LemonLDAP::NG.
iSfinx is a Web services based prototype of the Sfinx PIM. Sfinx is a personal knowledge and data manager which can manage your private data like contacts, events, notes, files, tasks, know-how, etc. Each data item is structured with abstract "slices", which are organized with a category hierarchy that you can define for your own needs. Every data item must be connected to some Sfinx object. Events can be connected to contacts, contacts to tasks, tasks to data sources, know-how, or notes, and so on. You can freely edit, delete, or reconnect them. Additional tags, which can be slices or other Sfinx objects, can also be attached to items, so any data you enter to Sfinx can be cross-connected with any other data or abstract category. A search engine helps you to navigate in this information ocean.