Apache Beehive Retired, Moved To Apache Attic

| by Gilad Manor Follow 0 Followers on Feb 23, 2010. Estimated reading time: 1 minute |

Last month, the committers of the Apache Beehive project voted to retire the project due to inactivity. The last release of Apache Beehive was version 1.0.2, which was released in December 2006.

The code which became the basis for the Beehive project was originally written by BEA as part of the WebLogic Workshop project, to draw attention and use of WebLogic 7.0 and 8.1. Eventually the codebase was donated as open source in the form of Beehive. Beehive attempted to simplify the usage of Java EE development by providing three key components:

  • NetUI - An automation layer which overlaid Apache Struts 1.x, and which allowed for easier managing of application flow
  • Controls framework - A framework which generated a lot of the boilerplate code which was required for accessing EJBs and web service APIs in older versions of Java EE
  • Web Service Metadata - A component which auto-generated web services APIs via annotations, and which was an implementation of JSR-181, which was eventually included in Java EE 5

In the announcement posted on Feb 10th, Henri Yandell suggested alternatives for the three components described above, including:

  • Struts2 or the Spring Web Flow to replace NetUI - Spring Web Flow is part of the Spring infrastructure and addresses issues like navigation rules and management of conversation states while facilitating modularization and reusability. Struts 2 is based off of WebWork, and supports building reusable UI templates such as form controls, UI themes, internationalization, dynamic form parameter mapping to JavaBeans, client/server side validation, etc.
  • The Spring Framework to replace the Controls framework - Spring supports accessing local or remote EJBs from the application web tier
  • The Axis2 JSR-181 implementation to replace Web Services Metadata - Apache Axis is a web service, SOAP and WSDL engine which provides annotation support for generating web services, and which handles both client- and server-side support for web services

Users of the Beehive project who wish to continue using this project may do so as part of their own development efforts, and the project site and codebase will remain accessible at Apache's attic.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you