Qwicket is a quickstart application for the wicket framework. Its intent is to provide a rapid method for creating a new wicket project with the basic infrastructure in place so that you can quickly get to the meat of your application rather than mucking with the plumbing of a wicket application. Currently, the system only supports spring and hibernate built with ant. Future plans include support for maven 2 and other persistence layers such as ibatis.
Parancoe is a Java meta-framework aggregating in an useful way Hibernate/JPA, Spring 2, Spring MVC and, for the AJAX support, DWR. Parancoe purpose is to give to developers a set of libraries ready to build standard web applications (which in most cases are just crud applications) without worrying of long and harmful configurations files. Parancoe will be composed of a full MVC stack.
SpringSource Application Platform is a completely module-based Java application server that is designed to run enterprise Java applications and Spring-powered applications with a new degree of flexibility and reliability. The SpringSource Application Platform is based on the new SpringSource Dynamic Module Kernel™ (dm-Kernel). The dm-Kernel provides a module-based backbone for the server, which also harnesses the power of Spring, Apache Tomcat and OSGi-based technologies
The "Clustered Remoting For Spring Framework" (or Cluster4Spring) is alternative implementation of remoting subsystem included into Spring framework.
Clustered remoting scheme
While implementation of remoting in Spring is great, it has several limitations that are quite important and must be taken into consideration when building large enterprise-level distributed system.
Briefly, these limitations relate to the point-to-point model of remoting supported by Spring - generally speaking, the client may use only one instance of remote service. It is obvious that having only such a scheme of remoting, it is hard to develop fault-tolerant systems and implement some kinds of load balancing.
Another feature, which is currently missing in remoting subsystem offered by Spring framework, is lack of the ability to dynamically discover remote services.
The main purpose of Cluster4Spring is to extend remoting system of Spring framework and overcome limitations mentioned above.
EasyBeans is an open-source Enterprise Java Beans (EJB) container hosted by the OW2 consortium. The License used by EasyBeans is the LGPL.
EasyBeans main goal is to ease the development of Enterprise Java Beans. It uses some new architecture design like the bytecode injection (with ASM ObjectWeb tool), IoC, POJO and can be embedded in OSGi bundles or other frameworks (Spring, Eclipse plugins, etc.).
It aims to provide an EJB3 container as specified in the Java Platform Enterprise Edition (Java EE) in its fifth version. It means that Session beans (Stateless or Stateful), Message Driven Beans (MDB) are available on EasyBeans.
The new persistence layer used by EJB 3.0 is now called Java Persistence API (or JPA). It replaces the CMP (Container Managed Persistence) model used by EJB 2.x. The default persistence provider used in EasyBeans is Hibernate Entity Manager or Apache OpenJPA but other JPA providers have been tested like for example Oracle TopLink Essentials.
How good is your software? jmove eases the understanding and valuation of the design and architecture of complex software written in java. It provides dependency analysis, metrics, design rule checking and impact analysis. Define your desired architecture model and check consistency with the implementation.
jmove offers a framework and an extendable set of tools to ease the understanding of the design and architecture of software systems and to provide support to control the software from this point of view. It is based on a model centric approach which allows to analyze different kind of sources like source code and byte code.
10gen is a new platform-as-a-service technology designed to help developers quickly and easily build dynamic, scalable, mission critical web sites and applications.
The 10gen software stack is analogous to Google App Engine in that it provides a new stack of tools (database, grid management, application server) that are purpose-built to run in a cloud environment.
Gracelets is a view/controller technology layered on top of Facelets/JSF. It complements the Facelets templating technology by allowing Groovy scripts to replace or be used in connection with normal Facelets source files and views.
The name came from combining the Gr in Groovy and replacing the F in Facelets with Gr, Groovy Facelets, or Gracelets (yeah, a no-brainer).
One of the inspirations behind Gracelets was the desire to use Groovy scripts, which have many practical applications for many java developers these days, and yet have all the power of Facelets and JSF behind the groovy script. Another inspiration was to at least have the option to develop quick solutions in a single file. Of course the Model-View-Controller concept is marvillous and it is important to keep things seperate, which can also be easily done with Gracelets. But sometimes it is nice not to be forced to do so just to prototype or develop some quick solution that one wants or needs, and Gracelets gives you that option. In other words, Gracelets works fine as simply a view technology in the MVC flow, but also allows you to do more in a single script if you so desire.
The main goal of Gracelets is to complement Facelets and provide more options, flexibility and efficiency to Facelets and JSF users and component developers. Since you can still use normal Facelet XHTML views and everything else you already have invested in JSF/Facelets, you are not forced to use Gracelets even though it is installed/configured. Thus you can choose exactly where you want to use Groovy Facelets/Gracelets in your application. Even inside Gracelet scripts, you can still access the full component/tag set already available in JSF/Facelets. Some of the possible practical uses of Gracelets could be (but is not limited to) the following:
Reverspring is a Java library that allows you to create Spring IoC XML files from POJO at runtime.
CoI stands for Control of Inversion: Reverspring just inverts the inversion of control mechanism of Spring Framework, allowing you to (re)write Spring descriptors starting from your Java objects. With Reverspring you can write process descriptors on XML files without re-inventing a new DTD or XML-Schema, but just using the well known Spring IoC syntax.
Welcome to JaValid
JaValid is an open source framework for validating your Java business objects. JaValid is licensed under the Eclipse Public License 1.0. JaValid 1.1-rc1 is the latest release.
JaValid is an annotation-based validation framework, which allows you to annotate your Java objects to introduce validation. JaValid can be used in any type of Java application (standalone application, web application etc). The framework currently provides full integration with the Spring Framework, Java Server Faces, Facelets, and any database. The framework can be extended easily, by means of extensions, and allows you to add your own validation constraints in addition to the ones shipping with the framework.
The framework is documented well (both the source and the general documentation), so check it out. To learn more, have a look on the documentation page.
The source and distributions are hosted on sourceforge, go to the downloads directly here. You may also want to check out the weblog, which contains some useful information, including several examples.
Have fun using JaValid!
The goal of Simple is to bring the power of simplicity to the world of server side Java. The primary focus of the project is to provide a truly embeddable Java based HTTP engine capable of handling enormous loads. Simple provides a truly asynchronous service model, request completion is driven using an internal, transparent, monitoring system.
This allows Simple to vastly outperform most popular Java based servers in a multi-tier environment, as it requires only a very limited number of threads to handle very high quantities of concurrent clients. Simple has consistently out performed both commercial and open source Java Servlet engines and has a fully comprehensive API that is as usable for experienced Java developers as it is for beginners. Best of all, Simple is completely free, and is released under the terms of the GNU Lesser General Public License, LGPL, which ensures its availability for use by open source and proprietary developers alike.
Oranjestad Spring is a series of helper classes and extensions for use with the Spring Framework. The current extensions are as follows:
* Spring Lightweight plugins
* External Beans
* Listener Based Dependency Injerction
The short answer is that Qi4j is a framework for domain centric application development, including evolved concepts from AOP, DI and DDD.
Qi4j is an implementation of Composite Oriented Programming, using the standard Java 5 platform, without the use of any pre-processors or new language elements. Everything you know from Java 5 still applies and you can leverage both your experience and toolkits to become more productive with Composite Oriented Programming today.
Exadel Flamingo provides a set of commands that help a developer to generate initial code. To bootstrap a project, a developer answers a few questions in a wizard. Based on these questions, a standard project is generated. Flamingo is based on Maven, therefore the new application is generated according to Maven conventions, making it easy for people familiar with Maven to navigate through the project.
The generated code provides all the necessary plumbing and connectivity from Flex or JavaFX to Seam or Spring. A developer only needs to focus on business functionality; Flamingo takes care of the rest. All communications between the user interface and Seam or Spring components are taken care of by Exadel Flamingo.
Exadel Flamingo also provides a set of Flex components that make it extremely convenient to support specific features of Seam on the client side.
JSF Flex goal is to provide users capability in creating standard Flex components as JSF components. So users would create the components as normal JSF components and the project will create the necessary SWC, SWF files and etcetera and link the values of the components back to the managed beans using JSON+Javascript and Actionscript. {standard Flex components has been open sourced through MPL license}
Currently many of the standard rich flex widgets (buttons, sliders, inputs [richTextEditor, textArea, ...], progressbars, colorpickers, various panels [accordion, tabBar, ...], and etcetera) have been written as intention of support.
[fleXive] is a JavaEE 5 open source (LGPL 2.1 or higher) framework for the development of complex and evolving (web-)applications. 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.
Based on the latest industry-standards like EJB 3, JSF, etc. [fleXive] should be your choice for building up your own new application.
This is an early implementation of JSR 303 (Bean Validation), a specification of the Java API for JavaBean validation in Java EE and Java SE.
The technical objective is to provide a class level constraint declaration and validation facility for the Java application developer, as well as a constraint metadata repository and query API.
This implementation is based on the validation framework of agimatec GmbH, that is in production for more than a year and offers additional features, like XML-based extensible metadata, code generation (JSON for AJAX applications), JSR303 annotation support.
For more information refer to the Wiki at Overview
Elastica is a highly efficient and extensible, rules-based load-balancer for JBoss that adds dynamic behavior to EJB load balancing. Rules can be defined to redirect EJB requests according to request data, server performance data, or even the time of day
nexusBPM is an open-source enhancement of JBoss's jBPM product suite. We have added many features to both the editor and the engine.
nexusBPM provides en enhanced editor experience with a variety of preconfigured nodes such as FTP, SQL, Excel and others. All nexusBPM nodes can participate in dataflow which is very easy to use. Using dataflow means that information created by one node can be used by another for processing, formatting, output or decision making. The nexusBPM editor can even communicate with the nexusBPM server andsupports drag and drop upload and download capabilities as well as remote run commands.
nexusBPM provides an enhanced engine with support for scheduling flows using quartz, executing nexusBPM nodes using message driven beans and custom commands.
Scannotation is a Java library that creates an annotation database from a set of .class files. This database is really just a set of maps that index what annotations are used and what classes are using them. Why do you need this? What if you are an annotation framework like an EJB 3.0 container and you want to automatically scan your classpath for EJB annotations so that you know what to deploy? Scannotation gives you apis that allow you to find archives in your classpath or WAR (web application) that you want to scan, then automatically scans them without loading each and every class within those archives
There are really 3 main classes to Scannotation: ClasspathUrlFinder, WarUrlFinder, and AnnotationDB. The first step in scanning for annotations is declaring what archives or what parts of your classpath you want to scan in. ClasspathUrlFinder has various ways to automatically find the URLs that make up your classpath. WarUrlFinder is similar but provides ways to get things from your WAR lib directory.
Once you find the URLs that make up your classpath, you feed them to AnnotationDB to scan and index. Its best to read the javadocs