[fleXive] is a Java EE 5 content repository aiming to support upcoming industry standards like CMIS. It strives to provide a holistic approach by offering a comprehensive set of tools and building blocks for building content-centric Web applications around a [fleXive] content repository. It speeds up development by easing many tedious and repetitive programming tasks and helping to keep your application(s) flexible during the development cycle and in production. It concentrates on enterprise-scale content modeling, storage, and retrieval, and includes comprehensive JSF support for displaying and manipulating these contents in (Web) applications. Key features include persistence, security, versioning, multi-language support, and scripting.
CodaServer is a database that makes building business applications easy. It uses a SQL-like language that lets you describe your workflow and business processes, and uses this information to enforce your business rules and guarantee data integrity. It also has a rich set of metadata commands so that your applications can get the information they need to build intelligent, process-aware user interfaces. CodaServer's listener is Web service-based, making it truly cross-platform, and it uses standard SQL databases for storing data, protecting your current investment.
[fleXive] CMS is a Java EE content management system based on JavaServer Faces 1.2. It combines the power of JSF XHTML templating with that of the Java EE 5 content repository, [fleXive]. Some highlights include dynamic JSF templating (Facelets), easy integration of custom logic with EJB or JSF beans, a modular structure, Maven support, generic data structures, and WebDAV and CMIS support. It incorporates all core [fleXive] features like security, versioning, multilinguism, and scripting.
TimeMachine Scheduler is a Java scheduler which can scale and run a high volume of jobs with many different types of schedules, such as repeating on a fixed interval or based on cron expressions. The scheduler can control the job executions with thread pools, and it can persist job data into different storage receptacles. Users may use the built-in schedule server with an easy-to-use configuration file, or developers may use it as a library to extend the scheduler and write custom jobs, schedules, or user services.