ojBoss
o
In the beginning

In the beginning there was EJBoss, an EJB Open Source Server. And then there were layers telling us that EJB was a trademark... well since we like what SUN does and we don't want to step on anyone's toe's we decided to change the name to jBoss by simply dropping the "e".

Sometimes fate has to hit you hard with a clue stick.

 
o
o
jBoss 1.0 (a.k.a EJBoss/NextGen)

jBoss 1.0, a.k.a EJBoss was started in March 1999 and reached 1.0 status in February 2000. The long march towards the promised land of 1.0'ness was not taken lightly. jBoss 1.0 established itself as a technological leader with many ease of use features pioneered here before finding their way to the broader audience of commercial container developers.  Mostly thanks to Rickard Oberg, the design of 1.0 introduced many standard setting features such as Proxy based deployment and distributed containers.

Marc Fleury had been working for almost 6 months on a traditional, compilation heavy approach to the container design, when Rickard came along with the logical skeletons and the dynamic proxies as the basis for a radically new design. Marc started coding feverishly and codenamed the container "NextGen" truly believing it was a blueprint of things to come, a "next generation" container.

 
o
o
jBoss 2.0

jBoss 2.0 is truly a 3rd generation container. It takes the patterns and ideas that were investigated in 1.0 and then does it right. Designed from the ground up to be modular, jBoss introduces yet again many ground breaking features such as the automated re-deploy but most importantly a plug-in approach to the container implementation. Borrowing from the success that met with Linux 2.0 and it's modular approach to Open Source software implementation, jBoss 2.0 is meant to be developed by distributed parties each working on a cleanly separated part of the server.

jBoss 2.0 also standardizes on JMX, the Java Management eXtension (TM) to offer standard interfaces to the management of its components as well as the applications deployed on it. Ease of use is still the number one priority here at jBoss and jBoss 2.0 will set a new standard.

 
o
o
Modular is good

jBoss 2.0 is meant for all usage, it's modular structure allow it to be embedded in applications with small footprint plugins. If you don't need the passivation in a 3rd party tool? take it out it is as simple as using the GUI that comes with it.

You are running a large ASP or a 24x7 IT shop? put the passivation right back in and you can sleep peacefully.

You have a favorite O/R tool you want to work with? glue plug-ins are in development and will enable you to drop your favorite tool to work with the container.

 
o
o

 

 
o
 
o
oInfo o
jBoss 2.0 is completely modular. This makes jBoss 2.0 an ideal solution for many different needs. Proxy based deployment makes jBoss one of, if not the, simplest tool of the industry. Beans and Applications running on top of jBoss need not be open sourced.
 
oThe Tasks o
Development of jBoss 1.0 has stopped and all development efforts have moved to jBoss 2.0. jBoss 2.0 is based on modular plugins. Testing documenting and coding are all needed on this new codebase. Come code the future!
 
o
 
o
o
Have a look at... o
Mailing lists
CVS
Binary