BOS BOS application framework of tools

Outline:
    application framework overview, BOS application framework Overall, BOS application framework detailed design, code structure and common applications, the development of common interface

framework (Framework) is reusable design of the whole or part of the system, showing among a set of abstract components and component instance the method of interaction; it defines the architecture of the application, illustrates the dependencies between the entire design, collaboration component, responsibility and control flow distribution, expressed as a set of abstract classes and methods for cooperation between instances
application framework refers to It achieved an unrelated business applications and the underlying common base functions and services and reusable components

metadata model is used to describe a business model structure data. Metadata includes the BOS solutions, packages, entities, relationships, queries, data tables, functions, business functions, enumeration, abnormal, and many other types of metadata.
In EAS, the metadata model MDA i.e., established the theoretical basis of MOF metadata system, through EAS model / design / development / implementation of the whole process. Metadata is the heart of the EAS, EAS quality is first determined by the metadata.
    BOS design, edit / maintain metadata, publishing Java code
    DEP Dynamic extensible platform by editing / metadata maintenance of documents to expand the development of
    mobile BOS, through metadata design of mobile terminal business functions
    get Affairs J2EE framework, access metadata attribute and cache
    ORMapping, sql statement generated by the metadata
    application framework, generate application logic code frame by a metadata
    permission / synchronization, authorization by the metadata / permissions / synchronization control
    workflow, via metadata designing business processes, process properties
    background transaction, the transaction content metadata definitions
    BOTP / DAP, the conversion rule is defined by metadata


Function (Facade) and business function (Function) is similar, except that the operating function is not bound to the entity, and the operational needs of business functions bound to a solid. Therefore, in processing dependent on an entity, e.g. the review document operation, using the business function (Function), without depending on the processing of a particular entity, such as closing end, use function (Facade).
BOS system metadata
    BizData-> MetaData-> MetaMetaData-> CoreMeta
    
    Hardcode / EntityObject.Relationship
    -------------
    Facade.entity / uiObject.entity / EntityObject.entity
    ------- ------
    Voucher.entity / Voucher.facade / VoucherListUI.ui

role:
abstract common component model
provides a standard of basic services
standardized programming model
to reduce large-scale application software system development difficulty
shorten development cycles
and improve development efficiency and quality

abstract common business logic; such as add, modify, delete and so on.
Standard integrated basic services; such as a network exclusive, permissions.
Standardized and unified programming model; such documents, and other basic information.
Unicode standards and interfaces;
reduce the complexity of development and improve development efficiency.
Designed to achieve maximum reuse and code reuse system.

bos overall architecture of the application presentation layer -orm-rpc protocol - the business logic - persistent object layer - the data layer

bos application framework detailed design
    master EAS business organizational model is a common processing mode and the specifications
    of the main service organizations that document service type
    main service organization to effect the document (including basic data) of
        data isolation, license type, service flow, context
    
     D: \ Kingdee \ eas \ client: EAS client store all files;
Ø D: \ Kingdee \ EAS \ client \ logs: storing log output, developers should focus error by log analysis.
 D: \ Kingdee \ eas \ client \ lib: stored codes Jar package;
Ø D: \ Kingdee \ EAS \ Client \ Metas store metadata Jar package;
Ø D: \ Kingdee \ EAS \ Client \ bin to store executable file;

    customers end of the graft: entire directory can be mounted or copied to another computer to use the directory, modify the file: [installation directory] \ eas \ client \ bin \ set -client-env.bat, wherein the modified variable "EAS_HOME, JAVA_HOME" is the actual path.
    
    Update the solution
    the solution retained Jar package metadata and code replica on the server, when the server is installed after the patch or update, both sides of the metadata and the code is no longer consistent solution may function update data from the server by synchronizing element Jar package and code into the solution.
    Solution to perform the update function method: Menu [program] [update] solutions. Update the solution with the operation of the "Import Solutions" Solutions need to select the root node before the update.
    Metadata:
    Data that describes data (model) for all data records stored model. BOS model data is not established in a single document, but rather a plurality of files divided in accordance with the contents stored in the model, all the model format (metadata) of the file in UTF-8 encoded XML document.
    A simple model contains metadata file are: editing interface EditUI, list interface ListUI, Entity Entity, relationship Relation, Table Table, Query Query, functions Function, integrated unit described BizUnit ,. There is also support for the metadata model and code development: Enumeration Enum, abnormal Exception, authority permission, log Log, business functions Façade, package Pakage.
    

    Client class inheritance hierarchy
        CoreUIObject: EAS base class for all UI from KDPanel derived, so UI can be easily embedded in other UI, does not include the business logic.
        CoreUI: parent of all UI interface objects, centralized processing services, general ui page
        ListUI: ordinals when thin UI interface object parent
        EditUI: All editing UI interface objects parent
        CoreBillListUI, CoreBillEditUI: parent business documents UI interface objects
        BillListUI, BillEditUI: CoreBillListUI, CoreBillEditUI subclass
        TreeListUI, TreeDetailListUI: when the tree hierarchy parent sequence thin UI interface object

    server object class inheritance hierarchy value
        PropertyContainer: abstract attribute defines a container storage structure EAS target value
        IObjectValue, AbstractBaseObjectValue: EAS for all values of the abstract parent class
        CoreBaseInfo: all the values of an object having an ID attribute abstract parent class

    server ORM object class inheritance hierarchy
        IORMModel, ORMObject: interface and implementation ORM-RPC protocol and service
        IBOSObject, AbstractBOSObject: Get BOS interfaces and to achieve the desired engine running context
        ICoreBase, CoreBase: abstract superclass of all objects ORM
        ICoreBillBase, CoreBillBase: abstract parent class for all business documents EAS ORM objects

    SessionBean: None series of operations interface status session Bean
    AbstractBizControllerBean: the basic operation realize EJB, database connection
    AbstractEntityControllerBean: ORMapping engine data access objects (DAO) and obtain call
    AbstractCoreBaseControllerBean: EAS specific traffic values corresponding to the object abstract parent class EJB