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.