Slashdot Mirror
Apache Beehive Buzz and Pollinate eclipse plug-in
John writes "Beehive is a new Apache project that simplifies Java 2 Platform, Enterprise Edition (J2EE) and Web services programming. This article shows how to get started with Beehive and offers a sneak preview of Pollinate, an Eclipse plug-in that creates Beehive applications."
Hello World is a good example for getting someone up to speed on a language, because it takes him through the most basic stuff -- creating a program, compiling and linking it, then invoking it -- without any unnecessary complexities.
It makes no sense to use Hello World as an example for a MVC framework, because in that case the complexities are necessary. The point of the system is to organize the complexity in a well factored design; sincer in HW there is nothing to factor, the reader is left wondering what the point of all the machinery is.
That said, this reminds me a lot of the approach Microsoft took to make MFC bearable -- which is to try to put a facade on the whole thing using an IDE.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
The article talks about how beehive sits on top of struts and makes a long and complex struts-config file a thing of the past.
That would be well and good, but it looks like in their example they are putting the same type of configuration information including flow control into hard coded controller classes instead. How is this any different? Let alone better that using an XML file? One of the main points of the struts-config is to allow the user to change page flow, permissions, navigation, validation options, using XML files that get interperted upon server startup so that these types of changes wouldn't require a new code deployment (and thus a long and arduous testing cycle).
Technology should innovate or at least attempt to build a better mouse-trap. I don't see how Beehive does either of the two. Perhaps there is a better explanation somewhere.
Ah, I see the subtlety of the humor was lost....
:-)
With that in mind (from the front page of Apache.org):
# HTTP Server (C)
# Ant (Java)
# APR (C)
# Cocoon (Java)
# DB
# Torque (Java)
# ObjectrRelationalBridge (Java)
# DB Commons (Nothing published, but has phrase "including but not limited to Java"
# Directory
# Apache Directory Server (Java)
# LDAP (nothing published)
# Naming (Java)
# AuthX (nothing published)
# ASN.1 (Java)
# Kerberos (Java)
# MINA (Multipurpose Infrastructure for Network Applications) (Java)
# Excalibur (Java)
# Forrest (Java)
# Geronimo (Java)
# Gump (Java, supports multiple language builds)
# Jakarta (Java)
# James (Java)
# Lenya (Java)
# Logging (Multiple languages)
# Lucene (Java)
# Maven (Java)
# MyFaces (Java)
# Perl (C)
# Portals (Java)
# SpamAssassin (Perl)
# Struts (Java)
# TCL (C)
# Web Services
# Axis (C++, Java)
# WS-FX (C++, Java)
# JaxMe (Java)
# jUDDI (Java)
# SOAP (Java)
# WSIF (Java)
# WSIL (Java)
# WSRP4J (Java)
# XML-RPC (Java)
# EWS (Java)
# Mirae (Java)
# Muse (Java)
# Scout (Java)
# Addressing (WS-FX subproject) (Java)
# Sandesha (WS-FX subproject) (Java)
# WSS4J (WS-FX subproject) (Java)
# Apollo (WS-FX subproject) (Java)
# Hermes (WS-FX subproject) (Java)
# XML
# Xerces (Java, C++, Perl, COM)
# Xalan (Java, C++)
# AxKit (C)
# Batik (Java)
# FOP (Java)
# Xang (JavaScript)
# SOAP (Java)
# Crimson (Java)
# XML-Security (Java, C++)
# Xindice (Java)
# XML Commons (Java)
# XMLBeans (Java)
Now I may have missed a few, but it looks like the majority of the Apache projects are developed in and for Java.
That doesn't bother me, but I wanted to ensure that the source of *my* amusement was obvious.