Beanlet – JSE Application Container – Beanlet and Jarcraft Confluence
Following the bile blog comments/discussion on XML wiring is for girls I found this very interesting link:
Beanlet – JSE Application Container – Beanlet and Jarcraft Confluence
Why use Beanlet?….These are the top ten reasons for using Beanlet technology:
1. Beanlet provides a unique agile non-intrusive container framework.
2. Beanlet API is concise and (soon) well documented.
3. Beanlet respects API compatibility.
4. Beanlet is easy to learn.
5. Beanlet integrates with most popular frameworks.
6. Beanlet is extensible, add your own plug-ins.
7. Beanlet promotes a defensive programming style.
8. Beanlet is open source.
9. Beanlet is free.
10. Nobody has ever beanlet down by it.
Just to let you know, beanlet is indeed very interesting!
The beanlet.org website has been put together right after releasing version beanlet version 0.1. The website hasn’t changed over the last 8 months, b/c focus has been on the first 1.0 release of beanlet. A 1.0 release candidate can be expected later this month.
This release candidate will be fully functional, that includes full Java Persistence API integration. JPA is integrated in an EJB-like fashion. It has support for both container managed and application managed EntityManagerFactories, including the Extended PersistenceContext (which is currently only supported for Stateful EJBs).
A beanlet demo will be released at the same time. Don’t worry, you will be notified once it is available