A programming model of a cohesive and easy usage is urgently needed to build J2EE applications. For new Java developers, just to build a simple application, you need to learn a lot of API; advanced J2EE developers must write the tedious pipeline code, tool designer is limited to how they simplified due to underlying complexity Experience. In addition, when Java Developers transfer J2EE to the service architecture for development and integration, they need next generation tools. The purpose of the Beehive (Hive Plan) is to meet these needs.
Beehive is a proposed open source project, which is based on the Workshop application framework. BEA has proposed to use Beehive to create the first cross container, easy-to-use programming model, and establish a J2EE and SOA application model. The Beehive project will provide a consistent, abstract and easy-to-tool-based programming model, and provide a way to build applications more effectively using the latest technologies provided by JDK 1.5. We expect this project to attract new users to build enterprise Java applications, and use some model to attract experienced J2EE programmers, which avoids these programmers to repeatedly write the same J2EE code.
Beehive is an extensible Java Application Framework, which has an integrated metadata-driven programming model for web services, web applications, and resource access. The framework utilizes the latest innovation of JDK 1.5, especially JSR 175 metadata annotations. The purpose of Beehive is to provide a one-stop resource for building consumer services and other enterprise resources. Components in the current plan include:
The Controls-Control architecture is a lightweight component framework based on annotation Javabeans that disclose a client model for accessing various J2EE resources types. The framework provides a large number of functions, including: JavaBean-based client access, configuring, automatic resource management, context services, and scalable design models for creating new control types through JSR-175 metadata and external configuration data.
l Netui - Netui Page Flow is a web application framework based on Apache Struts, with a single file programming model based on JSR-175-dollars. This page is built on the core Struts separation of the model / view / controller element and adds some features, such as automatic state management and integration with controls, XMLBeans, and JavaSerFaces.
l Metadata for Java Web services - this component is an implementation of JSR-181 specification and is a key part of the Beehive framework. JSR 181 uses JSR-175 metadata annotations in Java methods and classes to easily build web services.
Through Beehive, the Workshop Application Framework core will be available for other J2EE platforms. Developers using WebLogic Workshop will be able to use the Workshop metadata driver programming model to create web services, web applications, and Java controls, and then run these components on any J2EE application server. The initial version will run on Tomcat, and other platforms will be easily implemented. On May 24, 2004, we have seen Tomcat-based implementation on EWORLD.
Beehive makes Java developers succeed
l Investment protection by providing specific contractors and portability
w Provide users who are locked in application code assets by providing portable portability to non-BEA platforms to protect investments in application code assets.
w For development and deployment, choose technology and suppliers.
w can be ported to any application server.
w Desktence of a clear separation between the environment and the runtime environment, providing a wide range of tool options for developers.
l makes Java easier access
w Make Java and J2EE easier for the majority of developers.
W Metadata Drive Programming Model for Behavior Declaration / Abstract Specification.
l Build SOA
W Used to arrange and combine applications visualization, declaration, and service-based models.
l Java and Enterprise Application Constructs WEB applications based on MVC / Struts.
W Web Service.
W is used to simplify system integration and arrangement Java controls.
w Use the XML Beans with all-around XML in a Java friendly manner.
Compared to .NET easier, business Java development
Java Enterprise Application Development needs to be as simple as .NET, while maintaining richness, robustness and selectivity based on Java platform. Easy to use is more important because .NET and J2EE are available in enterprise development.
Almost two years ago, BEA introduced WebLogic Workshop to start to respond to these challenges. WebLogic Workshop combines traditional IDE by using the high productivity programming model provided by the application framework. By using declarative, metadata-driven programming models, the application framework abstracts the complexity related to developing Java and enterprise applications. In addition, Workshop's service-oriented development and integration examples indicate that it is a first development tool that is easy to promote interface abstraction. In other words, developers can easily construct applications with operating integrity, and it will not increase Time and easy to integrate with existing and future systems.
Almost two years ago, we started the standard process. Since then, the BEA has been driven JSR (JSR-181, JSR-207) and the standardization of Java annotation tools (JSR-175) in the Java community (JSR-175). However, the most urgent needs of Java communities is to make developing J2EE and enterprise applications easier and more accessibility. We continue to focus on JCP, but fast adoption and development of bold new programming models is not necessarily correct. BEA has long been using other tools, such as Oasis, WS-I, IBM early two-way standards, and open source projects other than JCP, thereby drive innovation and investment protection, and support customers to migrate to the next generation SOA deployment.
Standardized BEA model
This is another milestone in the long-term task of the BEA commitment to drive its industry leading innovation. BEA will continue its brand integration, and provide investment protection for customers through all appropriate tools. The standardized model is overview below.
Here is an example of this model:
protocol
l Bea / Microsoft / IBM WS- * Collaboration - (Before Standardization) WS- * family has been mainly designed by these three suppliers
l WS- * Standardization - W3C and Oasis
l WS- * Verification - Web Services Interoperability Organization, WS-i)
Programming model
L BEA / IBM Java Collaboration - announced in 2003 that the collaboration is based on the BEA / IBM / Microsoft Web service collaboration. It focuses on accelerating server-side Java API standardization, especially for SOA
l Java Community Process (JCP)
l European Computer Manufacturers Association (such as XScripts)
l W3C (such as XQuery)
l Oasis (such as BPEL)
Open source software (OSS)
Xmlbeans has been open last year, and is currently an Apache project.
Independent Software Developer (ISV)
ISV will also benefit from Beehive. Open source is accelerating advanced programming models and technologies provided by Beehive, as well as a way to broaden support between various developer tools and platform communities. Open source IDE does not complete this in a sufficiently satisfactory way. Abstract API complex applications have made this. By accelerating its acceptance, BEA improves the entire enterprise Java ecosystem and opens new market opportunities for BEA ISV and integrated partners and Java developers.
The application framework is of great significance in the following aspects:
l runtime frame
l Technical and supplier choices L from top to bottom transparency, easy control
l Make Java and J2EE easier for the majority of developers.
l Visualization, declaration, and service-based model used to arrange and combine applications.
l The explicit separation between the environment and the runtime environment.
The function of the frame is important:
l Need to be a service-driven programming model
l Data Drive Programming Model for Declaration / Abstract Specification for Behavior
w Synchronize (for "real-time" query).
w asynchronously (for business operations).
l web applications for simplified component models based on MVC / Struts, web services and support drag and drop; unified interconnect model
l Mix Java and XML to support tools and runtime environments seamless integration
Beehive's Java control maintains a special commitment to ISV. Now ISV can save development costs, using a simplified Java control user model, and can be ported to any other compatible J2EE container.
Workshop
Controls are also scalable - now there is more than
100
Home
ISV
Provide your own control, these controls are adopted
Workshop
Tools and appearances can support customization of value-added services
/
Orchestration. The most important thing is that when customers or
ISV
When building a control, the control can be in business process (from
Web
Application or portal to build
Web
Service) is heavy, or
WebLogic
Other other places in the application reuse.
