Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Apache Beehive

From Wikipedia, the free encyclopedia
This article is about a Java application framework. For theHadoop-based data warehouse infrastructure, seeApache Hive.
This articlecontainspromotional content. Please helpimprove it by removingpromotional language and inappropriateexternal links, and by adding encyclopedic text written from aneutral point of view.
See ouradvice if the article is about you and read ourscam warning in case someone asks for money to edit this article.
(October 2019) (Learn how and when to remove this message)
Apache Beehive
DeveloperApache Software Foundation
Final release
1.0.2 / December 4, 2006; 19 years ago (2006-12-04)
Written inJava
Operating systemCross-platform
TypeJava Application Framework
LicenseApache License 2.0
Websitebeehive.apache.org
Repository

Apache Beehive is a discontinued JavaApplicationFramework that was designed to simplify the development ofJava EE-based applications. It makes use of various open-source projects atApache, such asXMLBeans. Apache Beehive uses Java 5, includingJSR-175, a facility for annotating fields, methods, and classes so that they can be treated in special ways by runtime tools. It builds on the framework developed forBEA SystemsWebLogic Workshop for its 8.1 series. BEA later decided to donate the code to Apache.[citation needed]

History

[edit]

Version 8.1 of BEA's WebLogic Workshop includes several improvements over version 7.0. The previous version was focused on creating industrial-strength web services quickly, and it failed due to low adoption and use. For version 8.1, BEA created a whole new Integrated Development Environment (IDE), which helped programmers to developJava EE-based applications more quickly. The improvements in Version 8.1 over Version 7 garnered several awards.

Although Workshop 8.1 only had limited success, the WebLogic Workshop Framework, which was developed for the 8.1 version Workshop, was recognized as a solid framework. In order for it to be used with other Java EE-based application servers, BEA decided to open-source the project under the purview of theApache Software Foundation.The latest version of Beehive was released on December 4, 2006, and retired to Apache Attic in January 2010.

Beehive components

[edit]

Netui Page Flows

[edit]

This is an application framework built on top ofApache Struts that allows easier tooling and automatic updating of the various Struts configuration files.

Controls

[edit]

Controls are the core of the Beehive framework. A control can be defined as a program that can be used by the developer to access enterprise-level resources, such asEnterprise Java Beans (EJBs), web services etc. For example, consider accessing an oldlegacy EJB 2 bean. It involved a lot of routine code like getting access to a home interface, creating/finding an EJB using finder methods, and then accessing the remote methods of the bean. Using a control simplifies this process by handling most of the routine coding for the developer, letting them work on business logic rather than the inner-details ofJava EE technology. Controls are also useful to advanced developers, allowing them to concentrate on things like constructing aFacade to a complex set of application APIs. In essence, a control to a legacy EJB 2 been ensured that the developer could simply use the control and call any business method of the EJB, using it in the same way as any otherJava class. When EJB 3 came around, such simplification was already provided by the EJB specification itself,[1][2][3][4] And Beehive controls were of little further use here.[5][6] The Controls come with a standard set of controls wiz EJB Control, Web service Control, Database Control and JMS Control. Custom controls can also be developed, which in turn could make use of the controls already built-in.

Web services

[edit]

This third component of Beehive enables a developer to create web services using meta-data/annotations. By using meta-data/annotations one can create complexweb services utilizing features like conversation, state etc. Since all the metadata/annotations are in one file, it is easier to debug and maintain. Using this approach, any plain Java class can be converted into a web service just by the addition of annotations into the Java source files. This is based onJSR-181 which builds onJSR-175.

References

[edit]
  1. ^"This release made it much easier to write EJBs, using 'annotations' rather than the complex 'deployment descriptors' used in version 2.x. The use of home and remote interfaces and the ejb-jar.xml file were also no longer required..."EJB
  2. ^EJB 3 example
  3. ^"Enterprise Java Beans (EJB) 3.0 is a deep overhaul and simplification of the EJB specification."http://www.jboss.org/ejb3
  4. ^"... the heavyweight programming paradigm in EJB 2.x, the flawed persistence model in EJB 2.x entity beans..." "In our view, one of the most important changes in EJB 3.1 is the redefinition of EJBs as simple managed bean POJOs with additional services."http://blog.caucho.com/?p=384Archived 2010-11-23 at theWayback Machine
  5. ^"... the EJB 3 client model has essentially standardized much of the value-add that the [Beehive] EJB control offered in terms of simplifying the EJB 2.1 client model"http://markmail.org/message/mh43akcleflzes3r
  6. ^Andre McCulloch, "OK, these are great points that lead me to believe that and [sic] EJB3 control does not provide much value add for Beehive right now."http://markmail.org/message/ktec5f4gsbw22ijb

Bibliography

[edit]

External links

[edit]
Top-level
projects
Commons
Incubator
Other projects
Attic
Licenses
Retrieved from "https://en.wikipedia.org/w/index.php?title=Apache_Beehive&oldid=1329207129"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2026 Movatter.jp