JFOXPORTAL (JFOX portal) development plan
(
By huihoo.org JFOX project group)
First draft: jacky li (jianhua23@163.com)
1 Overview
JSR-168 specification description:
JSR-168 (Enterprise Portlet Specification 1.0 Final Draft Published on 2003-09-03, will be 2003-10-06 Final Approval Ballot) is a new Java portlet standard for portlet level development. The portlets followed by JSR-168 can be transplanted on other Portal Container. Site at JSR-168 specification: http://www.jcp.org/en/jsr/detail?id=168
Portlet description:
In the need for the customability of the portal, the portal component concept portlet is introduced. The portlet is a pluggable component, and the portlet has various definitions, JSPEED is submitted, the JSR-168 portlet API Specifications is defined as the portlet:
Portlets are a web component that can be managed by the container, which can generate dynamic content. Portlets can be easily inserted and run in a web application, portlets are a combined page that is designed to aggregate a large amount of content, for example: according to different users, different instances can be generated, and these instances are based on users The settings contain different contents, that is, to satisfy the user's ability.
2. The first stage: demand analysis and related document collection stages
Current OpenSource Enterprise Portal Analysis
Jetspeed
JetSpeed is an open source project organized by Apache (http://jakarta.apache.org/jetspeed), IBM's WebSphere Portal Server is based on JetSpeed for secondary development.
In order to achieve effective management and monitoring of portal content, JetSpeed's important content component slide introduces the concept of domain and namespace, controlling all resources, in SLIDE, Domain is a series of Namespace aggregates, it is similar The "/" root directory in the system, Domain can control the access rights of Namespace in which registered Namespace, and execute management work for initialization and connection of Namespace.
Namespace is a self-independent container that cannot contain or connect to other Namespace, each application system can be a Namespace, NameSpace contains independent data and security access mechanisms for these data.
Although JetSpeed provides a wealth of portal technology, it is more customizable, and its important content component SLIDE is also more difficult to understand. Its security control framework is not integrated with General J2EE, all of which are caused by JaaS. The difficulty of secondary development is carried out on the basis.
Liferay
Liferay (http://www.liferay.com) represents a complete J2EE application, using technologies such as Web, EJB, and JMS, especially its front interface part uses Struts framework technology, XML-based portlet configuration files can be freely dynamically Extended, using Web Services to support some remote information acquisition, use APAHCE Lucene to implement full-text search function.
Liferay's disadvantage is that it lacks a simple and clear architectural architecture design, Portlet design is more messy, and it has certain difficulties in the second development.
Jportal
Jportal (http://jportal.sourceforge.net) is the most implementation of the PORTAL implementation of JSR-168 SPEC. He used interceptor technology and Dynamic Proxy to implement portlet's plug-in design. He is currently just a prototype implementation and focuses on implementing Portal Container, does not have too much portlet implementation and design. The advantage is that its architecture is clear and easy to expand, but the gap between portal's industrial strength is relatively large, no distributed concept is a fatal place in his current architecture.
3. Second Phase: Technical Selection Stage Target: Try to overcome the problem of Liferay structural confusion, implement the portlet component JAR HotSpot feature. It is fully compliant with JSR-168 specification. Portal Container design with industrial strength. The difficulty of Portal is to maximize dynamic features and the maximum selectivity of the interface.
Technical selection of MVC layers and expression layers:
Jarkarta Struts 1.1: http://jakarta.apache.org/struts
Description: MVC B / S architecture implementation
Jarkarta Velocity 1.3.1: http://jakarta.apache.org/Velocity
Description: Alternative JSP's expressions
Logical layer technology selection:
EJB (Enterprise Java Bean): Compliance with EJB 2.1 specification.
Note: Use EJB's SessionBean and MessageDriveNBean mechanisms to achieve distributed feature requirements.
EJB server: JBoss Enterprise Server 3.2.x
Description: Open source J2EE application servers, the system will implement different J2EE application servers through xdoclets.
Technical selection of data persistence layers:
Hibernate 2.0.1: http://www.hibernate.org
Note: The implementation of the JDO 2.0 specification is implemented, using O / R mapping technology.
Portlet implementation technology selection:
JMX (Java Management Extension 1.3: http://java.sun.com/products/javamanagement/
Note: Java management extension is a framework for the application, device, system, etc.
Jakarta Commons Modeler: http://jakarta.apache.org/commons/modeler.html
Note: The model MBEAN meta information of the component is configured, and the basic implementation of the MBEAN class is provided for complex resource classes.
Log technology selection:
JAKARTA log4j: http://jakarta.apache.org/log4j
Description: The record package of the system log.
Jakarta Commons Logging: http://jakarta.apache.org/commons/logging.html
Description: Enhance the record package tool for system logs.
Test frame selection:
Junit: http://www.junit.org
Description: System Code Test Tools.
JAKARTA CACTUS 1.6 dev: http://jakarta.apache.org/cactus
Description: J2EE Test Framework, test the code of the server side.
Web service technology selection:
Apache soap: http://ws.apache.org/soap
Note: The open source implementation of Web Service SOAP is based on him to achieve the corresponding Web Service function.
Apache axis: http://ws.apache.org/axis
Description: The Web Service framework is a further implementation of SOAP.
Other technical selection:
XDoclet 1.2 Beta 2: http://xdoclet.sourceforge.net/ Description: AOP (Attribute Oriented Programming) is facing attribute programming to simplify the continuous integration between components. By generating deployment descriptors and supporting code, it is greatly reduced to reduce development time, which is the developer placed the focus on the application logic code.
Ant 1.5.4: http://ant.apache.org
Description: The source code batch compilation tool.
JDOM Beta 9: http://www.jdom.org
Description: XML parsing tool.
Lucene 1.2: http://jakarta.apache.org/lucene
Description: The full text search kit, has an indexing mechanism.
4. The third stage: Portal Container architecture design is a different Caching mechanism architecture:
Because Portal technology is very dependent on Web Service, the web service of Web Service is very large. If each request is network communication, it is undoubtedly low. We need to save some status data that often use frequently in memory, and the client has been continuously accessed in the validity period. The use of HashMap saved objects is the most basic idea implementation, but this can only realize the buffer mechanism of stand-alone system. Once Portal's data level reaches a certain degree, you must implement the "cluster" Caching mechanism of multiple servers.
One Point Login and Permissions Management:
Single landing is an important technology of Portal, granular issues for permission management.
5. Fourth stage: portlet functional design
JFOX Enterprise Portal Architect Analysis
1. Overall structure analysis
Portal is a web-based application. In general, Personalization, single-point landing, content sets of different sources, and representations of the hook information system. A collection refers to the action of integrating the content of different sources in a web page. A Portal must provide mature personalization characteristics to provide users with customized content. Portal can also have different types of portlets to create related content for different users.
2.Portal Container Implementation Analysis
Portal container runs the corresponding portal and provides them must have a running period. A portlet container carries the portlet and manages their running period, which provides persistent storage for portlet references. The portlet container obtains the appropriate request from Portal and executes its request in the portlet.
3. Good EJB design architecture
Consider:
JNDI Efficiency Consideration.
4.Portlet implementation analysis
Realize the corresponding portlet insertion technology based on dynamic proxy.
5.Portal Caching implementation
The core class is org.noah.cache.model.cache, by constructing a new cache (Object Obj), it will require Cache's object to assign a value to achieve the purpose of cache. This object can be obtained by cache.getObject (). In order to achieve distributed Cache purposes, the polymorphic Server can share the same Cache, using the database to persist these Cache.
6. Consider making a Service Framework to provide a variety of services needed, similar to Turbine's Service Framework.
