InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Apache Beehive Retired, Moved To Apache Attic

Posted by Gilad Manor on Feb 23, 2010

Sections
Development
Topics
Java ,
Web Frameworks
Tags
EJB ,
Spring ,
Java EE ,
Spring Web Flow

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.

No comments

Watch Thread Reply

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.