What is Beehive?

Welcome to Beehive! Our goal is to make J2EE programming easier by building a simple object model on J2EE and Struts. Using the new JSR-175 annotations, Beehive reduces the coding necessary for J2EE. The initial Beehive project has three pieces.

• NetUI: An annotation-driven web application programming framework that is built atop Struts. NetUI centralizes navigation logic, state, metadata, and exception handling in a single encapsulated and reusable Page Flow Controller class. In addition, NetUI provides a set of JSP tags for rendering HTML / XHTML and higher-level UI constructs such as data grids and trees and has first-class integration with JavaServer Faces and Struts.
• Controls: A lightweight, metadata-driven component framework for building that reduces the complexity of being a client of enterprise resources. Controls provide a unified client abstraction that can be implemented to access a diverse set of enterprise resources using a single configuration model.
• Web Service Metadata (WSM): An implementation of JSR 181 which standardizes a simplified, annotation-driven model for building Java web services.

In addition, Beehive includes a set of system controls that are abstractions for low-level J2EE resource APIs such as EJB, JMS, JDBC, and web services.

New patent grants a company to collect fee for the use of ajax, rich web, web2, etc

This is nasty! US patent system should either be revisited or demolished. A small company was grated a patent that can possibly restrict the public or "open-source" use of rich web based applications like ajax, web2, etc. What does that mean? Probably google, yahoo, macromedia, microsoft and all other rich content lib/application makers will have to pay a fee to this company for what they are doing now.

Below links will give you detailed information:
The patent 779831
Rich-media applications are designed and created via the Internet. A host computer system, containing processes for creating rich-media applications, is accessed from a remote user computer system via an Internet connection. User account information and rich-media component specifications are uploaded via the established Internet connection for a specific user account...

The company
Balthaser makes a web-based design tool called pro:FX that enables users to build their own web applications using an interactive system constructed with Flash. Balthaser's patent covers almost exactly that process, but it is broad enough to encapsulate web based design tools constructed with virtually any technology or framework ..

the discussion
Now any site that uses rich-media technology implementations, including Flash, Flex, Java, Ajax, and XAML, when the rich-media application is accessed on any device over the Internet, including desktops, mobile devices, set-top boxes, and video game consoles will need a licence.

in news

TOGAF, The Open Group Architecture Framework

TOGAF, The Open Group Architecture Framework, is an industry standard architecture framework that may be used freely by any organization wishing to develop an information systems architecture for use within that organization.

TOGAF has been developed and continuously evolved since the mid-90’s by representatives of some of the world’s leading IT customer and vendor organizations, working in The Open Group's Architecture Forum. Details of the Forum, and its plans for evolving TOGAF in the current year, are given on the Architecture Forum web site.

@link
@certification

Rule Engines for dynamic business logic

This is similar to the prolog interpreter I used in my acadamics. But integrating a rule based engine in an application framework model with a backing server like weblogic, provides lot of power to the enterprise.

Business applications often require logic that changes frequently to meet the dynamic needs of the enterprise. While this logic can be coded in Java, the resulting application cannot be quickly adapted when change is required. BEA WebLogic Portal includes a rules engine that, together with a WebLogic Integration business process, provides an alternative solution that allows rapid
changes to business logic without changing Java code. In this article, we review how the rules engine works and the steps required to incorporate it into a WebLogic Integration (WLI) process. We also describe how JavaBeans can be used in the rules engine to describe an arbitrary set of objects for the rules to act on and provide actions for back-end processing. Finally, we describe how the Datasync facility of WebLogic Portal can dynamically update a set of rules on a running system without redeploying the application.

@complete article