I briefly talk about the overall architecture, there may be no place to be, please refer to it, I think OFBIZ is very known for the establishment of large and medium-sized product systems. Generally, large-scale applications are not more than three models: database, processor service service, and processes Definition, these three aspects OFBIZ is the foundation of OFBIZ: OFBIZ is primarily divided into several engines: Entity and Service and workflow. Entity is very similar to entity beans in EJB, which is responsible for all database parts in the system, and there are two important class GenericDelegator, which is specifically responsible for data sources; GenericValue is a specific product. We look at the service, genericEngine is the core, including synchronous services and asynchronous services, these two services are synchronous processing of servlet / session beans in J2EE, and JMS asynchronous services. All Service is assigned by ServiceDispatcher, requiring synchronous services, assigning genericasyncengine to serve, while checking if the user has the permissions of such services. Each genericdelegator corresponds to a serviceDispattcher. ModeElService This is a class after breaking the Request Signal, and the corresponding service is removed according to the Requesthanlder, which has three modes in IN / OUT / INOUT. Let's take a look at the service configuration class below:
The above service name is UserLogin, which uses Java Engine. This service requires two input parameters (from request): login.username and login.password. If these two parameters do not meet the name and object type, this service will not Call, some parameters may not be sent to the service, these parameters need to be defined as Optional.
After this service is called, the output OUT parameter will be detected, and of course only tagged request is detected, of course, this service may not return any parameters.
Ofbiz also has its own MVC model similar to Struts.
Although Ofbiz's Entity Engine is good, you can hang a lot of specific applications, but I feel that it seems to be more convenient to develop JBuilder CMP. Off Service Framework is the most worthy of reference.
The step is like this: 1. Write XPDL file 2. Import the XPDL file to the XPDL Reader provided under WebTools to the database 3. Add to add the Workflow in the service definition file, service type is Workflow4. Write you Some custom importation Tools used in XPDL files, I use procedure, ready, to implement operations for application data .5. If you use the limitService, you have to write LimitService, usually I use LimitService To achieve timeout processing. 6. Finally, some Test Unit use Service Engine to do some tests, the main purpose is to see if Transitions in XPDL is correct. My document is always written, just some points, hope You are useful. I suggest you look at XPDL in OFBIZ first, you will make it easy to get a little bit. OFBIZ_HOME / COMMONAPP / SRC / ORG / OFBIZ / CommonApp / Order / Order / ORDERPROCESSXPDL.XML reads it might want to see WFMC About Interface One Article
