Inspired by EJB3 and Spring, Beanlet delivers an IoC enabled application container offering the best of both worlds. Beanlet's programming model looks similar to that of EJB3, but gives you the flexibility of Spring at the same time. The Beanlet architecture supports JTA transactions, the Java Persistence API, JNDI, Web integration and the Spring Framework.
If your software project only requires a subset of features of a full blown EJB server, you should probably be looking for a solution like Beanlet. Beanlet brings many of the features of EJB to the world of the Java Standard Edition without the restrictions and limitations that are a logical result of the distributed nature of EJB. As a JSE Application Container, Beanlet can run both stand-alone and embedded inside Applet containers, Servlet containers, EJB containers or regular JSE applications.
Beanlet has a clear and concise API with a high power to weight ration. The API consists mainly of interfaces and annotations. Similar to EJB3, Beanlet components can be marked with these annotations to provide class specific configuration. Additionally, schema constrained XML configuration can be used to override existing annotations, or to mark your POJOs with new annotations. This XML configuration maps directly to the annotations - all annotations can be expressed by a single XML-element.
Why use Beanlet?
These are the top ten reasons for using Beanlet technology:
- Beanlet provides a unique non-intrusive application container for Java components.
- Beanlet delivers IoC using both XML and annotations.
- Beanlet allows specifying annotations through XML.
- Beanlet API has a high power to weight ratio.
- Beanlet is easy to learn.
- Beanlet integrates with most popular frameworks.
- Beanlet promotes a defensive programming style.
- Beanlet is open source.
- Beanlet is free.
- Nobody has ever beanlet down by it.
Getting started with Beanlet.
The HelloWorld class demonstrates how easy it is to write a beanlet. Notice the that the beanlet looks similar to an EJB3-style enterprise bean.
The Inject annotation lets the container initialize the logger field. The Run annotation instructs the container to activate the beanlet by invoking the execute method.
In addition, beanlets can be defined by XML. Instead of using annotations, the HelloWorld class could offer the same functionality with the XML file listed below.
Summarized, beanlets can be defined by annotations, XML or a mixture of both. Develop beanlets quick and easy using annotations, or apply XML to create beanlets in a non-intrusive way - with no dependencies on the Beanlet API.
Keep checking back on this site as a tutorial will become available shortly. It will be a quick guide that explains how to set up a Beanlet environment and it will covers all Beanlet basics. For now, please check out the demo to get started.
Beanlet software is licensed under terms of the GNU Lesser General Public License (LGPL).