GASwerk - Geronimo Application Server Assemblies
GASwerk provides production ready solutions based on proven OpenSource components.
Three server assemblies based on Apache Geronimo Application Server are available. Each of them solving a particular problem.
GASwerk SOA Stack is a powerful feature-rich SOA assembly for agile businesses that want to bring their IT department closer to their business processes. GASwerk SOA provides an Enterprise Service Bus for connectivity and an business process engine to model all the processes.
GASwerk Spring is focused on developer needs. It provides a Spring framework deployment feature. Equipped with GASwerk Spring, your Geronimo Application Server is able to directly deploy Spring Applications to your server.
GASwerk JMS is a Messaging Cluster based on Javas Messaging Service (JMS). It is a powerful, scalable solution for companies where message throughput and reliability is critical.
And of course you could use all the GASwerk pieces together or only parts of the whole stack.
Geb GAS!
What is Ebean?
Ebean is a Object Relational Mapping Persistence Layer written in Java (Open Source LGPL license).
* Providing the features of EJB3's JPA (and more)
* No container required
* JPA compatible ORM mapping (@Entity, @OneToMany, ...)
Why use Ebean?
Ebean provides a simpler approach to Object Relational Mapping. It does this by not requiring session objects such as JPA EntityManager, JDO PersistenceManager, Hibernate Session, Toplink ClientSession.
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.
[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.
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
Granite Data Services (GDS) is a free, open source (LGPL'd) alternative to Adobe® LiveCycle® (Flex™ 2+) Data Services for J2EE application servers. The primary goal of this project is to provide a framework for Flex 2+/EJB 3/Seam/Spring/Guice/POJO application development with full AMF3/RemoteObject benefits.
It also features a Comet-like data push implemention (AMF3 requests sent over HTTP) and ActionScript3 code generation tools (Ant task and Eclipse builder).
Dedicated service factories are available for:
* EJB 3 (session beans that return entity beans),
* Seam (with identity security and conversation/task support),
* Spring (with Acegi security and entity beans support),
* Guice/Warp (with entity beans support),
* Simple Java classes (aka POJO) interactions.
GDS is designed to be lightweight, robust, fast, and highly configurable.
EJBs in Scala schreiben
Was spricht eigentlich dagegen, eine EJB in Scala zu implementieren? Um diese Frage zu beantworten, habe ich ein Demo-Projekt aufgesetzt, in dem ich zwei EJBs in Scala implementiere.
Upgrading JBoss 4 to JBoss 5 with Java 5 to Java 6
The information presented here comes from an effort to upgrade a Java enterprise application to the most current versions of all of its parts; primarily to get onto Java 6. Its starting system specifications were the following:
This is again a small JMS configuration stuff we have to do in JBoss 5. There is considerable difference in doing it in JBoss 5 compared to JBoss 4 and don’t expect our old configuration to work well with JBoss 5 without any change. In JBoss 5 they are using JBoss Messaging in place of JBoss MQ. You can read a detailed post on migrating from JBoss 4 to JBoss 5 here.