CN105700892A - Component layering extension method based on inheritance relationship - Google Patents
Component layering extension method based on inheritance relationship Download PDFInfo
- Publication number
- CN105700892A CN105700892A CN201610096305.6A CN201610096305A CN105700892A CN 105700892 A CN105700892 A CN 105700892A CN 201610096305 A CN201610096305 A CN 201610096305A CN 105700892 A CN105700892 A CN 105700892A
- Authority
- CN
- China
- Prior art keywords
- component
- configuration information
- contract
- dimension configuration
- development arrangement
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a component layering extension method based on an inheritance relationship, belongs to the field of enterprise-level application development, and provides a set of extensible layering architectures to solve the technical problem about how to better summarize and extract business logics in the enterprise-level application software. According to the technical scheme, the method comprises the first step of component classification, wherein components are classified and include contract components and implementation components; the second step of dimensionality configuration information during the component operation period; the third step of layering extension on the development layer, namely patch upgrading on the development layer; the fourth step of component calling calculation during the operation period, that is, a component calling engine searches for a specific implementation component to be called according to the dimensionality configuration information on the highest development layer in the dimensionality configuration information during the operation period.
Description
Technical field
The present invention relates to enterprise-level application development field, specifically a kind of component delamination method based on inheritance。
Background technology
In enterprise-level application development field, in order to reach the purpose of service logic precipitation, multiplexing and decoupling, substantially all carrying out business model, service logic is packaged into different components, this is the usual manner of service logic modeling。Enterprise-level application demand is ever-changing, is difficult to immobilize。Therefore, the service logic how can better summarize and extract in enterprise-level application software, and provide a set of extendible layer architecture, is the enterprise-level application development field problem of needing solution badly。
Summary of the invention
The technical assignment of the present invention is for above weak point, a kind of component delamination method based on inheritance is provided, solve the service logic how can better summarize and extract in enterprise-level application software the problem that a set of extendible layer architecture is provided。
The technical solution adopted for the present invention to solve the technical problems is: a kind of component delamination method based on inheritance, comprises the steps:
(1), the classification of component: by introducing the concept inherited, component being classified, component is divided into contract component and realizes component two types；Wherein, the user of component, contract component can only be used when definition, it is impossible to directly use and realize component；Otherwise, it will not possess dynamic lookup and realize the delamination ability of class；Wherein, respectively realize would be likely to occur between component inheritance, it is achieved between component and contract component, there is interface implementation relation。
(2), the dimension configuration information of component runtime: the dimension configuration information of component is contract component and realizes the tie of dynamic routing between component, for specifying under different dimensions configuration information, realizes component corresponding to contract component；The corresponding dimension configuration information of each contract component, development arrangement is the built-in dimension configuration information of acquiescence；
Wherein, development arrangement includes standardized product layer, industry customization layer, affiliate or third party's extension layer and end user's customization layer；
The dimension configuration information of component, is mark belonging to development arrangement, namely represents an identity of different development arrangement, and this mark is with different levels, and the closer to standardized product layer, its level is more low, and priority is more low；The closer to end user's customization layer, its level is more high, and execution priority is more high；
(3), the delamination of development arrangement, i.e. the patch upgrading of development arrangement: during patch upgrading, each layer of dimension configuration information of each development arrangement retains；When the product of different development arrangement carries out patch upgrading, the dimension configuration information of this patch place development arrangement can only be revised so that the dimension configuration information of each development arrangement is independent of each other；Dimension configuration information corresponding to each development arrangement, it is simply that what it to call implements the mark of component；
(4), the component of runtime calls calculating: refer to that component calls engine and implements component in the runtime according to what the dimension configuration information lookup of the highest development arrangement in dimension configuration information to be called。Wherein, when only standardized product development layer, component just is scheduling running according to the dimension configuration information of standardized product development layer, when there is the delamination of user's customization layer or other layers, component calls engine and just realizes component accordingly according to the dimension configuration information scheduling of user's customization layer or other layers, and the principle of lookup is exactly that the height according to development arrangement carries out, the closer to end user's customization layer, development arrangement is more high, and the priority of its dimension configuration information is also more high。When thus achieving different level development in not revising metadata or code under the premise of component invoking mark, according to different development arrangement dimension configuration informations, carry out, according to the dimension configuration information of the highest exploitation level, the purpose implementing component that dynamic lookup to call。
As preferably, the contract component in described step (1): the concept being similar in programming interface, for describing service, configuration and the attribute that this component externally provides；Contract component is exactly an interface class in programming language, and it is the business model of an interface class in service logic, is that its metadataization describes, method in component and attribute, correspond to the method for this interface class and attribute declaration。
As preferably, described step (1) realizes component: being similar in programming to realize the concept of class, it achieves the contract that contract component is declared, and these contracts have been carried out concrete implementation；Realize component in programming language be exactly one achieve interface corresponding to contract component realize class；One contract component is corresponding one or more realizes component, and one realizes the corresponding one or more contract components of component。
As preferably, the dynamic calculating step of described step (4) component runtime is as follows:
1., component calls engine and starts working；
2., judge whether to be called be contract component:
If (a) contract component, then perform following steps:
(a1), the highest development arrangement is obtained；
(a2) the dimension configuration information corresponding to the highest development arrangement, is obtained；
(a3) that, calls dimension configuration information realizes component；
(a4), component calls engine power cut-off；
B () if not contract component, then directly performs step (a3) and step (a4)。
Compared to the prior art a kind of component delamination method based on inheritance of the present invention, has the advantages that
1, the present invention is applicable for use with business model mode and develops the development field of enterprise-level application, the method mainly calls support delamination for starting point with component, provide a kind of flexible, the general method that dynamic calculation to call concrete component under concrete business scenario, by introducing the concept inherited, component is divided into contract component and realizes component two types, by dimension configuration information, achieve the component delamination method that dynamic controls, make user under the basis of institute's component invoking in not revising basic product layer metadata and code, mode by dimension configuration information, realize the dynamic adjustment to service logic, thus reaching the purpose of hierarchical-development；
2, in enterprise-level application development field, software development would generally be divided into different development arrangement, and the development arrangement of the present invention includes standardized product layer, industry customization layer, affiliate or third party's extension layer and end user's customization layer；Need synthetic operation between different levels, and can not influence each other；The closer to standardized product layer, its demand gets over generalization, requires more high to the extensibility of software architecture；The closer to end user's customization layer, its demand is more personalized, and execution priority is more high。
As can be seen here, the present invention has the features such as reasonable in design, simple in construction, easy to use, one-object-many-purposes, thus, have good value for applications。
Accompanying drawing explanation
Below in conjunction with accompanying drawing, the present invention is further described。
Accompanying drawing 1 is contract component and the inheritance schematic diagram realized between component；
Accompanying drawing 2 is component configuration schematic diagram；
Accompanying drawing 3 is component runtime dynamic calculation flow chart。
Detailed description of the invention
Below in conjunction with the drawings and specific embodiments, the invention will be further described。
Embodiment 1
As shown in figure 1 and 2, a kind of component delamination method based on inheritance of the present invention, comprise the steps:
(1), the classification of component: by introducing the concept inherited, component being classified, component is divided into contract component and realizes component two types；Wherein, the user of component, contract component can only be used when definition, it is impossible to directly use and realize component；Otherwise, it will not possess dynamic lookup and realize the delamination ability of class；
Contract component: the concept being similar in programming interface, for describing service, configuration and the attribute that this component externally provides；Contract component is exactly an interface class in programming language, and it is the business model of an interface class in service logic, is that its metadataization describes, method in component and attribute, correspond to the method for this interface class and attribute declaration。
Realize component: being similar in programming to realize the concept of class, it achieves the contract that contract component is declared, and these contracts have been carried out concrete implementation；Realize component in programming language be exactly one achieve interface corresponding to contract component realize class；One contract component is corresponding one or more realizes component, and one realizes the corresponding one or more contract components of component。
(2), the dimension configuration information of component runtime: the dimension configuration information of component is contract component and realizes the tie of dynamic routing between component, for specifying under different dimensions configuration information, component is realized, in order to implement component what runtime dynamic calculation to be called corresponding to contract component；The corresponding dimension configuration information of each contract component, development arrangement is the built-in dimension configuration information of acquiescence；
Wherein, development arrangement includes standardized product layer, industry customization layer, affiliate or third party's extension layer and end user's customization layer；
The dimension configuration information of component, is mark belonging to development arrangement, namely represents an identity of different development arrangement, and this mark is with different levels, and the closer to standardized product layer, its level is more low, and priority is more low；The closer to end user's customization layer, its level is more high, and execution priority is more high；
Wherein, the dimension Key corresponding to development arrangement is that acquiescence increases, and does not allow to delete and amendment, and what the user of certain development arrangement only allowed to revise the contract component corresponding to the development arrangement dimension Key of its place implements component, i.e. dimension values。Dimension configuration information is as shown in the table:
(3), the delamination of development arrangement, i.e. the patch upgrading of development arrangement: during patch upgrading, each layer of dimension configuration information of each development arrangement retains；When the product of different development arrangement carries out patch upgrading, the dimension configuration information of this patch place development arrangement can only be revised so that the dimension configuration information of each development arrangement is independent of each other；Dimension configuration information corresponding to each development arrangement, it is simply that the mark of its concrete " the realizing component " to call；
(4), the component of runtime calls calculating: refer to that component calls engine and implements component in the runtime according to what the dimension configuration information lookup of the highest development arrangement in dimension configuration information to be called。Wherein, when only standardized product, component just is scheduling running according to the dimension configuration information of standardized product, when there is the delamination of user's customization or other layers, component calls engine and just realizes component accordingly according to the dimension configuration information scheduling of user's customization layer or other layers, and the principle of lookup is exactly that the height according to development arrangement carries out, the closer to end user's customization layer, development arrangement is more high, and the priority of its dimension configuration information is also more high。When thus achieving hierarchical-development in not revising metadata or code under the premise of component invoking mark, dimension configuration information according to different development arrangement, carries out, according to the dimension configuration information of the highest exploitation level, the purpose implementing component that dynamic lookup to call。
As shown in Figure 3, the dynamic calculating step of component runtime is as follows:
1., component calls engine and starts working；
2., judge whether to be called be contract component:
If (a) contract component, then perform following steps:
(a1), the highest development arrangement is obtained；
(a2) the dimension configuration information corresponding to the highest development arrangement, is obtained；
(a3) that, calls dimension configuration information realizes component；
(a4), component calls engine power cut-off；
B () if not contract component, then directly performs step (a3) and step (a4)。
Embodiment 2: for sales order list
(1) when, developing based on step (1) standardized product in embodiment 1, first, the contract component (contract component A) of development and sale order list, state this contract component and method, attribute list, and specify its corresponding interface class (InterfaceA)；After contract component development completes, the sales order list developing standardized product development layer realizes component (realizing component A), this realizes realizing class (SalesOrderClassA) and to realize the interface class corresponding to contract component corresponding to component, and contract component A is called in formulation in sales order list table, and different buttons is corresponded on the distinct methods of contract component A。
(2) when, developing based on step (2) standardized product in embodiment 1, dimension values (realizing component A) under dimension (SYS) representated by specified value product development layer, dimension configuration information now is as shown in the table:
| Contract component | Development arrangement | Realize component |
| Contract component A | SYS (standardized product) | Realize component A |
(3), based on the step (4) in embodiment 1, after configuration standard product, it does not have delamination, so the runtime can be run realizes component A。
(4), based on the step (2) in embodiment 1, for sales order list interface, different industries has different demands, single standard product can not meet the customer demand of different industries, just for the industry that can not meet demand, different industry customization versions should be developed；The sales order list now having only to develop this specific industry DSP1 realizes component (realizing component B), this realizes realizing class (SalesOrderClassB) and to realize the class SalesOrderClassA that realizes of component A corresponding to component, and carries out the service logic regarded as output controlling of oneself。
(5) dimension values (realizing component B) under dimension (DSP1), representated by designated trade customed product layer, dimension configuration information is as shown in the table:
(6), based on the step (4) in embodiment 1, now there is standardized product layer and DSP1 industry customization layer simultaneously, there is delamination, so it is realize component B that the runtime can navigate to the component that realizes to call according to the height of development arrangement。
(7), the spread step of other levels and scheduling mechanism with the development procedure of above-mentioned DSP1 industry customization version and scheduling mechanism, repeat no more herein。
By detailed description of the invention above, described those skilled in the art can be easy to realize the present invention。It is understood that the present invention is not limited to above-mentioned two kind detailed description of the invention。On the basis of disclosed embodiment, described those skilled in the art can the different technical characteristic of combination in any, thus realizing different technical schemes。
Except the technical characteristic described in description, it is the known technology of those skilled in the art。
Claims (4)
1. the component delamination method based on inheritance, it is characterised in that: comprise the steps:
(1), the classification of component: component is classified, and component is divided into contract component and realizes component two types；
(2), the dimension configuration information of component runtime: the dimension configuration information of component is contract component and realizes the tie of dynamic routing between component, for specifying under different dimensions configuration information, realizes component corresponding to contract component；The corresponding dimension configuration information of each contract component, development arrangement is the built-in dimension configuration information of acquiescence；
Wherein, development arrangement includes standardized product layer, industry customization layer, affiliate or third party's extension layer and end user's customization layer；
The dimension configuration information of component, is mark belonging to development arrangement, namely represents an identity of different development arrangement, and this mark is with different levels, and the closer to standardized product layer, its level is more low, and priority is more low；The closer to end user's customization layer, its level is more high, and execution priority is more high；
(3), the delamination of development arrangement, i.e. the patch upgrading of development arrangement: during patch upgrading, each layer of dimension configuration information of each development arrangement retains；When the product of different development arrangement carries out patch upgrading, the dimension configuration information of this patch place development arrangement can only be revised so that the dimension configuration information of each development arrangement is independent of each other；Dimension configuration information corresponding to each development arrangement, it is simply that what it to call implements the mark of component；
(4), the component of runtime calls calculating: refer to that component calls engine and implements component in the runtime according to what the dimension configuration information lookup of the highest development arrangement in dimension configuration information to be called。
2. a kind of component delamination method based on inheritance according to claim 1, it is characterised in that: the contract component in described step (1): for describing service, configuration and the attribute that this component externally provides；Contract component is exactly an interface class in programming language, and it is the business model of an interface class in service logic, is that its metadataization describes, method in component and attribute, correspond to the method for this interface class and attribute declaration。
3. a kind of component delamination method based on inheritance according to claim 1, it is characterised in that: described step (1) realizes component: it achieves the contract that contract component is declared, and these contracts have been carried out concrete implementation；Realize component in programming language be exactly one achieve interface corresponding to contract component realize class；One contract component is corresponding one or more realizes component, and one realizes the corresponding one or more contract components of component。
4. a kind of component delamination method based on inheritance according to claim 1, it is characterised in that: the dynamic calculating step of described step (4) component runtime is as follows:
1., component calls engine and starts working；
2., judge whether to be called be contract component:
If (a) contract component, then perform following steps:
(a1), the highest development arrangement is obtained；
(a2) the dimension configuration information corresponding to the highest development arrangement, is obtained；
(a3) that, calls dimension configuration information realizes component；
(a4), component calls engine power cut-off；
B () if not contract component, then directly performs step (a3) and step (a4)。
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610096305.6A CN105700892A (en) | 2016-02-22 | 2016-02-22 | Component layering extension method based on inheritance relationship |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610096305.6A CN105700892A (en) | 2016-02-22 | 2016-02-22 | Component layering extension method based on inheritance relationship |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105700892A true CN105700892A (en) | 2016-06-22 |
Family
ID=56223408
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610096305.6A Pending CN105700892A (en) | 2016-02-22 | 2016-02-22 | Component layering extension method based on inheritance relationship |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105700892A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7007266B1 (en) * | 2002-01-08 | 2006-02-28 | Quovadx, Inc. | Method and software system for modularizing software components for business transaction applications |
| CN102087679A (en) * | 2011-03-02 | 2011-06-08 | 电子科技大学 | Component technology-based product modeling method |
| CN102221998A (en) * | 2011-06-07 | 2011-10-19 | 北京大学 | Method for extending EJB container in component running support platform |
| CN104239102A (en) * | 2014-09-15 | 2014-12-24 | 腾讯科技（深圳）有限公司 | Operation method and device of application program |
-
2016
- 2016-02-22 CN CN201610096305.6A patent/CN105700892A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7007266B1 (en) * | 2002-01-08 | 2006-02-28 | Quovadx, Inc. | Method and software system for modularizing software components for business transaction applications |
| CN102087679A (en) * | 2011-03-02 | 2011-06-08 | 电子科技大学 | Component technology-based product modeling method |
| CN102221998A (en) * | 2011-06-07 | 2011-10-19 | 北京大学 | Method for extending EJB container in component running support platform |
| CN104239102A (en) * | 2014-09-15 | 2014-12-24 | 腾讯科技（深圳）有限公司 | Operation method and device of application program |
Non-Patent Citations (5)
| Title |
|---|
| 刘丹: "基于分层的过程构件分类描述与检索研究", 《软件工程师》 * |
| 刘丹: "基于分层的过程构件分类描述的研究与应用", 《计算机应用研究》 * |
| 和力等: "基于构件和模式的多层次软件复用技术", 《计算机应用研究》 * |
| 田容雨: "基于软件构件技术的Web系统开发平台的研究", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
| 许兆祥等: "基于构件的分层体系结构模型的研究与应用", 《山西电子技术》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10373217B2 (en) | Order management system with decoupling of fulfillment flow from fulfillment topology | |
| CN105138326B (en) | A kind of method and system for realizing sql dynamic configuration based on ibatis | |
| CN103645919A (en) | Method for extending functions of management information system through plugins | |
| CN110612509A (en) | Personalization of virtual assistant skills based on user profile information | |
| CN104657164B (en) | Software upgrading treating method and apparatus | |
| CN105631019A (en) | Metadata extension method and device | |
| CN105975277A (en) | Template-based mixed cloud elastic telescoping set building method | |
| CN115469881A (en) | A method and system for configuring, releasing and invoking business functions of a low-code platform | |
| CN104881461A (en) | Rapid data storage method | |
| CN109710235B (en) | Transaction implementation system and method based on Java intelligent contract service logic | |
| CN104700187A (en) | Bill generation method | |
| CN103677790B (en) | Software function modifying method | |
| CN103107919B (en) | A kind of Internet resources modeling method and system | |
| CN101046746A (en) | Code management in a distributed software development environment | |
| CN102215264A (en) | Method and device for supporting multi-tenancy data and service customized running | |
| CN105700892A (en) | Component layering extension method based on inheritance relationship | |
| CN104978170A (en) | Multi-agent system generating method based on graphical expression | |
| CN102945264A (en) | Method for intelligently starting distributed transaction | |
| CN114880013A (en) | A method and device for processing configuration information of a business process | |
| CN104407843A (en) | A dependency inversion optimization method for decoupling high-level and low-level modules | |
| TWI579782B (en) | Service management method | |
| CN107765655B (en) | Method, system and readable medium for extending MES function by message routing system | |
| CN105183447A (en) | A Lightweight Process Engine Implementation Method | |
| CN109636324B (en) | Electronic service contract processing method and device | |
| CN104239008B (en) | Parallel database management system and design |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160622 |