CN109901817A - A kind of software architecture system - Google Patents

A kind of software architecture system Download PDF

Info

Publication number
CN109901817A
CN109901817A CN201711309851.4A CN201711309851A CN109901817A CN 109901817 A CN109901817 A CN 109901817A CN 201711309851 A CN201711309851 A CN 201711309851A CN 109901817 A CN109901817 A CN 109901817A
Authority
CN
China
Prior art keywords
unit
service
plug
request
business plug
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.)
Withdrawn
Application number
CN201711309851.4A
Other languages
Chinese (zh)
Inventor
王雅文
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhenjiang Common Software Development Co Ltd
Original Assignee
Zhenjiang Common Software Development Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zhenjiang Common Software Development Co Ltd filed Critical Zhenjiang Common Software Development Co Ltd
Priority to CN201711309851.4A priority Critical patent/CN109901817A/en
Publication of CN109901817A publication Critical patent/CN109901817A/en
Withdrawn legal-status Critical Current

Links

Abstract

The present invention provides a kind of software architecture systems, the software architecture system is based on OSGI specification and REST principle is realized, it include: management of monitor module, for monitoring all business plug-in units and/or service in OSGI container, business plug-in unit is used to execute corresponding service logic according to external request of data;Management module is relied on, is relied on for providing and managing the service of the OSGI between multiple business plug-in units;Service management module executes service logic for controlling business plug-in unit, controls the publication and stopping of the service in OSGI container;Route distribution module, for receiving the request of data from browser, its corresponding processing method is determined according to the numerical value of the extended attribute of request of data, and request of data is distributed to the business plug-in unit corresponding to the processing method, it is handled by the business plug-in unit, or is handled according to the default rule of REST principle.According to the technical solution of the present invention, the Development of Modular management applied to web, mobilism configuration and extension may be implemented.

Description

A kind of software architecture system
Technical field
The present invention relates to business data processing technical fields, in particular to a kind of software architecture system.
Background technique
In traditional web application and development, due to the birth defect on framework, realize that component-based development is difficult, and do not have The specification of standard goes to constrain, and causes software complexity higher and higher, and component reusing technology is difficult, is difficult to decouple, and causes development efficiency It is low.Meanwhile for the software development architecture of existing web application, system unstable factor is difficult to control, and hot plug difficulty is very Greatly, when a certain module occurs abnormal or cannot use, other modules is frequently can lead to and be unable to normal use even delay machine.
Therefore, it is necessary to a kind of new technical solution, the Development of Modular management applied to web may be implemented, mobilism is matched It sets and extends.
Summary of the invention
The present invention is based on the above problems, proposes a kind of new technical solution, the module applied to web may be implemented Change development management, mobilism configuration and extension.
In view of this, the invention proposes a kind of software architecture system, the software architecture system be based on OSGI specification and REST principle realizes, the system comprises management of monitor module, for monitor all business plug-in units in OSGI container and/or Service, the business plug-in unit are used to execute corresponding service logic according to external request of data;Management module is relied on, for mentioning It services and relies on for the OSGI between the multiple business plug-in units of management;Service management module, for controlling the business plug-in unit Service logic is executed, controls the publication and stopping of the service in the OSGI container, and realize in the OSGI container The static resource management of resource plug;Route distribution module, for receiving the request of data from browser, if the data are asked It asks that there are extended attributes, then its corresponding processing method is determined according to the numerical value of the extended attribute of the request of data, and by institute It states request of data and is distributed to business plug-in unit corresponding to the processing method, handled by the business plug-in unit, expanded if it does not exist Attribute is opened up, then is distributed according to the default rule of REST principle to corresponding business plug-in unit.In the technical scheme, it uses OSGI specification and REST principle erect the OSGI frame of the software development for web application.By in frame plug-in unit and/ Or the monitoring of service, it can recognize the plug-in component operation in frame and rely on situation, to realize the hot plug to plug-in unit;Pass through The module of the web generated application is conducive to avoid depending on unduly between plug-in unit to the dependence control of the plug-in unit in frame Change design and mobilism adjustment;By the route distribution to request of data, to be conducive to from browser (client) Request it is timely, effectively handle.
In the above-mentioned technical solutions, it is preferable that further include middleware module, the middleware module specifically includes: format Submodule is managed, for the request of data to be uniformly mapped in PageJSON object, and by browser described in return value It is JSON character string that returned data, which is uniformly encapsulated as ResultData object and the data format of the returned data,;Request turns Send out submodule, for by the request of data received be converted to REST request, with by the route distribution module according to institute The numerical value for stating the PageJSON extended attribute of REST request determines its corresponding processing method, and REST request is distributed to Corresponding to the business plug-in unit of the processing method, handled by the business plug-in unit.In the technical scheme, by being asked to data The conversion and unified management for the format asked, it is preferably simultaneous so as to be carried out to the web application using traditional, non-OSGI framework Hold.
In the above-mentioned technical solutions, it is preferable that core inserter is provided in the system, the management of monitor module passes through The core inserter realizes the monitoring to the business plug-in unit and/or service.In the technical scheme, exist in OSGI frame Core (core) plug-in unit, then can directly using the core inserter in system business plug-in unit and/or service monitor.
In the above-mentioned technical solutions, it is preferable that the management module that relies on also is pair inside each business plug-in unit Dependence is provided as between, is specifically included: creating an IocContext class when system starts for specified business plug-in unit, and Corresponding instance object is explained according to the configuration of the IocContext class, and manages the Life Cycle of the instance object Phase realizes customized extension point, then utilizes pair that the customized extension point is inside the specified business plug-in unit Dependence is provided as between.In the technical scheme, dependence management also is carried out to the object inside business plug-in unit, be advantageously implemented pair The dynamic management and hot plug of business plug-in unit.
In the above-mentioned technical solutions, it is preferable that the route distribution module is also used to: the business plug-in unit on present node It is unavailable or dish out specific exceptions when, the request of data is distributed to the business plug-in unit of another enabled node.In the technical side In case, route distribution module can either realize the distribution in node, additionally it is possible to the distribution operation between node be realized, thus favorably In the success rate that raising handles request of data.
In the above-mentioned technical solutions, it is preferable that the clothes that the service management module passes through Hook Mechanism unified management publication Business.In the technical scheme, be conducive to the stability of lift frame using Hook Mechanism.
In the above-mentioned technical solutions, it is preferable that the service of the service management module publication is REST service, specified industry Business plug-in unit includes: associated with the specified business plug-in unit using the process of service management module publication REST service Similar integral infrastructure service resource (BaseServerResource), and by the specified business plug-in unit according to default configuration item or According to the configuration item marked and explaining in real time, corresponding REST service is issued.In the technical scheme, using of the invention The server of frame or the service of backstage publication are REST service, so that unified service type, is conducive to the stabilization of frame Property and scalability.
In the above-mentioned technical solutions, it is preferable that the configuration item includes at least one of or combinations thereof: Service name, end Mouth, connection number.
In the above-mentioned technical solutions, it is preferable that further include: dependent status judgment module, for judging the specified industry Whether business plug-in unit depends on restful plug-in unit, if relying on, is issued according to the corresponding configuration item of the restful plug-in unit Otherwise REST service is issued according to default configuration item.
In the above-mentioned technical solutions, it is preferable that further include: resource plug expansion module, for defaulting mapping ruler not When meeting current business demand, the method in custom interface provided according to the resource plug, the extension address URL and reality are provided Mapping between source path.In the technical scheme, additionally it is possible to the resource plug in frame is extended, to be adapted to reality When business demand.
By above technical scheme, the Development of Modular management applied to web, mobilism configuration and extension may be implemented.
Detailed description of the invention
Fig. 1 shows the block diagram of the software architecture system of embodiment according to the present invention;
Fig. 2 shows the schematic diagrames of the deployment architecture of the software architecture of embodiment according to the present invention;
Fig. 3 shows the schematic diagram of the OSGI system framework of embodiment according to the present invention;
Fig. 4 A shows the schematic diagram of PageJSON data structure;
Fig. 4 B shows the schematic diagram of ResultData data structure;
What the HTTP service that Fig. 5 shows embodiment according to the present invention was requested flows to schematic diagram.
Specific embodiment
To better understand the objects, features and advantages of the present invention, with reference to the accompanying drawing and specific real Applying mode, the present invention is further described in detail.It should be noted that in the absence of conflict, the implementation of the application Feature in example and embodiment can be combined with each other.
In the following description, numerous specific details are set forth in order to facilitate a full understanding of the present invention, still, the present invention may be used also To be implemented using other than the one described here other modes, therefore, protection scope of the present invention is not by described below Specific embodiment limitation.
Fig. 1 shows the block diagram of the software architecture system of embodiment according to the present invention.
As shown in Figure 1, the software architecture system 100 of embodiment according to the present invention, the software architecture system 100 is based on OSGI specification and REST principle realize that the system 100 includes: management of monitor module 102, for monitoring the institute in OSGI container There are business plug-in unit and/or service, the business plug-in unit is used to execute corresponding service logic according to external request of data;It relies on Management module 104 is relied on for providing and managing the service of the OSGI between multiple business plug-in units;Service management module 106, Service logic is executed for controlling the business plug-in unit, controls the publication and stopping of the service in the OSGI container, Yi Jishi Now to the static resource management of the resource plug in the OSGI container;Route distribution module 108 comes from browser for receiving Request of data, if the request of data there are extended attribute, is determined according to the numerical value of the extended attribute of the request of data Its corresponding processing method, and the request of data is distributed to the business plug-in unit corresponding to the processing method, by the business Plug-in unit is handled, if it does not exist extended attribute, then is distributed according to the default rule of REST principle to corresponding business and inserts Part.In the technical scheme, the OSGI frame of the software development for web application is erected using OSGI specification and REST principle Frame.By the monitoring to plug-in unit and/or service in frame, it can recognize the plug-in component operation in frame and rely on situation, from And realize the hot plug to plug-in unit;By the dependence control to the plug-in unit in frame, so that depending on unduly between plug-in unit is avoided, Be conducive to the modularized design and mobilism adjustment of the web generated application;By the route distribution to request of data, thus favorably In to the request from browser (client) it is timely, effectively handle.
In the above-mentioned technical solutions, it is preferable that further include middleware module 110, the middleware module 110 is specifically wrapped It includes: form management submodule 1102, for the request of data to be uniformly mapped in PageJSON object, and by return value institute It is JSON character that the returned data for stating browser, which is uniformly encapsulated as ResultData object and the data format of the returned data, String;Request forwarding submodule 1104, for the request of data received to be converted to REST request, by the routing point The numerical value for the PageJSON extended attribute that hair module is requested according to the REST determines its corresponding processing method, and will be described REST request is distributed to the business plug-in unit corresponding to the processing method, is handled by the business plug-in unit.In the technical solution In, by the conversion and unified management of the format to request of data, so as to the web using traditional, non-OSGI framework It is preferably compatible using carrying out.
In the above-mentioned technical solutions, it is preferable that core inserter, the management of monitor module 102 are provided in the system The monitoring to the business plug-in unit and/or service is realized by the core inserter.In the technical scheme, in OSGI frame There are core (core) plug-in units, then can directly using the core inserter in system business plug-in unit and/or service supervise It listens.
In the above-mentioned technical solutions, it is preferable that the dependence management module 104 is also for inside each business plug-in unit Dependence is provided between object, is specifically included: creating an IocContext class when system starts for specified business plug-in unit, And corresponding instance object is explained according to the configuration of the IocContext class, and manage the Life Cycle of the instance object Phase realizes customized extension point, then utilizes pair that the customized extension point is inside the specified business plug-in unit Dependence is provided as between.In the technical scheme, dependence management also is carried out to the object inside business plug-in unit, be advantageously implemented pair The dynamic management and hot plug of business plug-in unit.
In the above-mentioned technical solutions, it is preferable that the route distribution module 108 is also used to: the business on present node Plug-in unit it is unavailable or dish out specific exceptions when, the request of data is distributed to the business plug-in unit of another enabled node.In the skill In art scheme, route distribution module can either realize the distribution in node, additionally it is possible to realize the distribution operation between node, thus Be conducive to improve the success rate for handling request of data.
In the above-mentioned technical solutions, it is preferable that the service management module 106 passes through Hook Mechanism unified management publication Service.In the technical scheme, be conducive to the stability of lift frame using Hook Mechanism.
In the above-mentioned technical solutions, it is preferable that the service that the service management module 106 is issued is REST service, is specified Business plug-in unit using the service management module 106 publication REST service process include: and the specified business plug-in unit Associated Similar integral infrastructure service resource (BaseServerResource), and by the specified business plug-in unit according to default Configuration item or according to the configuration item marked and explaining in real time, issues corresponding REST service.In the technical scheme, it uses The server of frame of the invention or the service of backstage publication are REST service, so that unified service type, is conducive to frame The stability and scalability of frame.
In the above-mentioned technical solutions, it is preferable that the configuration item includes at least one of or combinations thereof: Service name, end Mouth, connection number.
In the above-mentioned technical solutions, it is preferable that further include: dependent status judgment module 112, it is described specified for judging Whether business plug-in unit depends on restful plug-in unit, if relying on, is sent out according to the corresponding configuration item of the restful plug-in unit Otherwise cloth REST service is issued according to default configuration item.
In the above-mentioned technical solutions, it is preferable that further include: resource plug expansion module 114, in default mapping ruler When not meeting current business demand, the method in custom interface provided according to the resource plug extends the address URL and reality Mapping between resource path.In the technical scheme, additionally it is possible to the resource plug in frame is extended, to be adapted to Real-time business demand.
The present invention is desirable with the advantage of OSGI specification and REST principle, realizes to the prominent of traditional software architecture system It is broken, design stablize, efficiently, mobilism, modularization, scalability, it is practical based on OSGI software architecture.
Wherein, OSGI (OpenServiceGatewayInitiative) open service gateway initiative is really one and is joined by OSGI Alliance initiates, using Java as the dynamic modularity specification of technology platform.Industry realizes that the platform of OSGI specification mainly has at present ApacheFelix, EclipseEquinox, Knopflerfish etc..In fact, OSGI is not only a kind of technology or specification, more It is theory, the method for a kind of Software Architecture Design.The building at least following advantage of the software architecture based on OSGI: it is standardizing Framework, under the unified constraint of component standard, go to realize component reusing technology and reinforce the self constrainting ability of software architecture;More it is applicable in In team's agility collaborative development;Stability, the scalability of lift frame, to achieve the purpose that effective Improving The Quality of Products.
And REST (RepresentationalStateTransfer) is doctor RoyFielding in he rich in 2000 A kind of software architecture style proposed in scholar's paper.Web services are considered as resource by REST, can uniquely be marked by its unique URI Know.The Main Specification of REST includes client/server, stateless, caching, unified interface, hierarchical system and on-demand code Deng.For REST service is with respect to SOAP, XML-RPC, more light weight, simple, while it being also able to satisfy the exchanging visit of heterogeneous platform, have The reusable characteristic of height.
Therefore, by the utilization to OSGI specification and REST principle, the structure module specification in standard can be easy to It constrains lower bootstrap person and realizes modular fractionation, reuse, increase to efficiently control software complexity, reinforce framework Restraining force.
Below in conjunction with Fig. 2 to Fig. 5, the software architecture system based on technical solution of the present invention is described in detail. Specifically, in the examples below, the ApacheFelix for following OSGI standard criterion will be used as OSGI platform, and be based on This Platform integration Restlet constructs software architecture.
Fig. 2 shows the schematic diagrames of the deployment architecture of the software architecture of embodiment according to the present invention.
As shown in Fig. 2, the deployment architecture of the software architecture of embodiment according to the present invention includes:
OSGI container 204, for receiving the HTTP request of the transmission of browser 202.OSGI container 204 is to be based on ApacheFelix platform is established according to REST code requirement, wherein comprising just like business plug-in unit 206 etc., for realizing tool The service logic etc. of body.For the specific composition and function of OSGI container 204, it is described in detail below in conjunction with Fig. 3.
It also include J2EE container 208 in the software component, wherein including several war packets.For the skill of this field Art personnel are it is understood that for J2EE container 208, usually after doing what a web application, after being wrapped into It is deployed in J2EE container 208;And in technical solution shown in Fig. 2, J2EE208 is actually for using traditional platform The web application of (specifically referring to difference and the platform of the software architecture of the application) exploitation carries out compatible middleware, specifically such as The format of HTTP request for issuing to browser 202 carries out unified conversion etc..
Fig. 3 shows the schematic diagram of the OSGI system framework of embodiment according to the present invention.
As shown in figure 3, the concrete structure schematic diagram of the OSGI container 204 in Fig. 2 is shown, including:
Route distribution device 302, for the request of data (such as HTTP request) from browser to be routed and distributed. Specifically, by checking execution method required by request of data, to be distributed to corresponding business plug-in unit 304, with into The specific business logic processing of row.
Business plug-in unit 304 receives the request of data that route distribution device 302 is distributed, and executes specific business logic processing Work.
Service managerZ-HU 306, provides extension mechanism, and each business plug-in unit 304 is needed to realize specific service logic, supports The dynamic release of service and stopping etc..
Resource plug (i.e. ResourceBundle) 308, for publication, the treatment process of service logic etc. for service, Resource required for providing.Wherein it is possible to which being extended extension point based on open source HTTPService310 is mainly extended resources The mapping of mapping ruler, that is, between the address URL and real resource path, if default mapping ruler meets business demand, business Bundle does not need to extend, and resource is directly deposited in associative directory according to default rule;If desired it customizes, then needs to realize money The method in custom interface that source bundle is provided.
Console 314 is managed, or is module warehouse, for the core inserter by being provided using frame (corebundle) 312 monitor OSGI containers in each plug-in unit, service whole life cycle, specifically by ContextManager class It realizes.The specific implementation principle of snoop-operations is BundleContext by registering customized ServiceListener (service Monitor), the realization such as BundleListener (plug-in unit monitorings);Second is that by the order built in ApacheFleix platform by program Execute the operation to plug-in unit.
According to the technical solution of the present invention, what core needed to realize actually includes " six unifications ", it may be assumed that uniform data mould Type is provided unified data interaction model, including request, returned data object by frame;Unified request interactive mode;Unified clothes Business style, unified REST service issue mechanism is provided by frame;Unification component relies on, and provides unified service by frame and relies on Mechanism, IOC mechanism;Unified static resource treatment mechanism, frame provide unified resource registering, administrative mechanism;Unified modules storehouse Library supports dynamic disabling, increases, updates, Unload module.
Unified data model: for page data, traditional SpringMVC, Struts are often different page requests Create multiple view or form, the request data that real page comes is exactly a list or required parameter nothing but, therefore can be with Page request data are uniformly mapped in PageJSON object, wherein PageJSON data structure is as shown in Figure 4 A.Server-side Or backstage returns to the data of the page and is all encapsulated as ResultData object, finally return that the page data format equally For JSON character string, wherein ResultData data structure is as shown in Figure 4 B.For general business functional processing module, only It needs to above-mentioned 2 class object set associated traffic data, it is other to be handled by unified frame.
Unified request interactive mode: based on unified data model, therefore the data format of front and back interaction is JSON word Symbol string, the request of the page are unified for post request (certain frame itself also supports get request etc.).
Uniform service style, the i.e. service of server-side or backstage publication are REST service, and the details of publication is as follows: if One business plug-in unit needs to issue REST service, only needs correlation Similar integral BaseServerResource (infrastructure service resource) simultaneously The configuration items such as Service name, port, connection number are marked by way of note according to actual needs (if not marking note, frame Frame uses default configuration item).It is unified as restfulbundle (restful plug-in unit, unified for being carried out to the style of service) Issue the realization principle of rest service: when business plug-in unit starts, restfulbundle dynamically can judge whether business plug-in unit relies on Restfulbundle is preferentially issued according to its configuration if relying on, is otherwise just issued by default configuration.Based on business feature, greatly General 90% request is all post or put request, therefore has done resource impact extension to this two methods and supported, if request The value of PageJSON extended attribute extra is not null, then frame restfulbundle forwards requests to extra to automatic Specified method goes to execute;Otherwise logical process is executed by the method for direct request.Under normal conditions, on a certain node Restfulbundle distributes routing REST request in container.But, there is also the clothes of business bundle on single node Business is available, but executes to dish out during the logic operation of method and specific exceptions (RestUnusedException) or suddenly can not With the request can be distributed on another enabled node by route distribution device at this time.I.e. there are double routing functions for route distribution device: The routing routed (between i.e. different nodes is routed between (routing and distribution of i.e. same intra-node), container in container and is divided Hair).
Unification component rely on: based on open source component framework iPOJO be extended, frame arrange between each business plug-in unit according to Rely be OSGI service rely on (the business plug-in unit in service logic there are hierarchical relationship forbid packet rely on or complete plug-in unit according to Rely), and OSGI service is relied on and is managed by primary iPOJO, the dependence between the internal object of business plug-in unit is by customized expansion Machine plotting is handled.Customized extension point utilizes SpringIoc principle, creates one when frame starts for each business plug-in unit Then IocContext explains instantiation related object according to the configuration of each class, and manages the life cycle of object.
Unified static resource processing: resource plug (i.e. ResourceBundle) is based on open source HTTPService and is expanded Exhibition.Extension point is mainly the mapping of extended resources mapping ruler, that is, between the address URL and real resource path, if default mapping rule Then meet business demand, then business plug-in unit does not need to extend, and resource is directly deposited in associative directory according to default rule;If needing It customizes, then needs to realize the method in the custom interface of resource plug offer.
Unified modules warehouse: module warehouse is exactly the management console of frame, the core bundle provided using frame (corebundle) whole life cycle for monitoring each bundle in OSGI container, service, specifically by ContextManager class It realizes.Specific implementation principle is BundleContext by registering customized ServiceListener, BundleListener Deng realization;Second is that the operation by the order built in Fleix by program execution to bundle.
What the HTTP service that Fig. 5 shows embodiment according to the present invention was requested flows to schematic diagram.
As shown in figure 5, based on the software architecture system (or OSGI frame) that technical solution of the present invention is established, for The process that HTTP service request is handled is as follows:
It is assumed that issuing the request of some HTTP service by browser 501, then there are two kinds of situations, in a kind of situation, by complete It is handled based on the web application that technical solution of the present invention generates, is then directly transferred to route distribution device 504;Another feelings Under condition, if being handled by traditional web application, it is transmitted to middleware 502, after being handled by middleware 502, then is forwarded To route distribution device 504.
Middleware 502 is mainly to carry out unified encapsulation of data format to the HTTP service request from browser 501, then REST request is sent to OSGI container according to mapping ruler.Mapping ruler supports dynamic configuration.Therefore, right by middleware 502 The format of HTTP service request carries out unified encapsulation, allows the invention to be compatible with traditional web application, have good Compatibility.
Route distribution device 504 provides extension, Hook Mechanism.Support business plug-in unit, can also be by using the route distribution of default Business plug-in unit goes to extend, and frame is managed collectively the service externally issued by Hook Mechanism.Specifically, route distribution device 504 Processing method required for requesting according to HTTP service carries out route distribution.
Infrastructure service resource 506, matching HTTP service request is to the corresponding method of business plug-in unit, to carry out specific business Logical process.
For example by HTTP service request distribution to business plug-in unit 508A, then service logic is executed by business plug-in unit 508A Reason;And when business plug-in unit 508A return as specific exceptions or suddenly it is unavailable when, then route distribution device 504 can be by HTTP service The business plug-in unit being distributed on another node, such as business plug-in unit 508B are requested, to promote the reliability of entire frame.
The technical scheme of the present invention has been explained in detail above with reference to the attached drawings, according to the technical solution of the present invention, can be realized Below the utility model has the advantages that
1) modularization can be effectively controlled software complexity and increase, avoid or delay especially for the complicated system integration Framework corruption.
2) mobilism solves hair version halting problem.
3) scalability, stability are more preferable.
4) the old project of this scheme is used, it is very smooth to move to OSGI, and it is very small to be applied to framework impact.
The foregoing is only a preferred embodiment of the present invention, is not intended to restrict the invention, for the skill of this field For art personnel, the invention may be variously modified and varied.All within the spirits and principles of the present invention, made any to repair Change, equivalent replacement, improvement etc., should all be included in the protection scope of the present invention.

Claims (10)

1. a kind of software architecture system, the software architecture system is based on OSGI specification and REST principle is realized, which is characterized in that The system comprises:
Management of monitor module, for monitoring all business plug-in units and/or service in OSGI container, the business plug-in unit is used for root Corresponding service logic is executed according to external request of data;
Management module is relied on, is relied on for providing and managing the service of the OSGI between multiple business plug-in units;
Service management module executes service logic for controlling the business plug-in unit, controls the service in the OSGI container Publication and stopping, and realize the static resource management to the resource plug in the OSGI container;
Route distribution module, for receiving the request of data from browser, if there are extended attribute, roots for the request of data Its corresponding processing method is determined according to the numerical value of the extended attribute of the request of data, and the request of data is distributed to correspondence In the business plug-in unit of the processing method, handled by the business plug-in unit, if it does not exist extended attribute, then according to REST principle Default rule be distributed to corresponding business plug-in unit.
2. system according to claim 1, which is characterized in that further include middleware module, the middleware module is specific Include:
Form management submodule, for the request of data to be uniformly mapped in PageJSON object, and will be described in return value It is JSON character that the returned data of browser, which is uniformly encapsulated as ResultData object and the data format of the returned data, String;
Request forwarding submodule, for the request of data received to be converted to REST request, by the route distribution The numerical value for the PageJSON extended attribute that module is requested according to the REST determines its corresponding processing method, and by the REST Request is distributed to the business plug-in unit corresponding to the processing method, is handled by the business plug-in unit.
3. system according to claim 1, which is characterized in that be provided with core inserter, the monitoring pipe in the system Manage monitoring of the module by core inserter realization to the business plug-in unit and/or service.
4. system according to claim 1, which is characterized in that the dependence management module is also each business plug-in unit Dependence is provided between internal object, is specifically included: creating one when the system starts for specified business plug-in unit IocContext class, and corresponding instance object is explained according to the configuration of the IocContext class, and manage the example The life cycle for changing object, realizes customized extension point, is then the specified industry using the customized extension point Dependence is provided between object inside business plug-in unit.
5. system according to claim 1, which is characterized in that the route distribution module is also used to: on present node Business plug-in unit it is unavailable or dish out specific exceptions when, the request of data is distributed to the business plug-in unit of another enabled node.
6. system according to any one of claim 1 to 5, which is characterized in that the service management module passes through hook The service of mechanism unified management publication.
7. system according to any one of claim 1 to 5, which is characterized in that the clothes of the service management module publication Business is REST service, and specified business plug-in unit includes: using the process of service management module publication REST service
Similar integral infrastructure service resource associated with the specified business plug-in unit, and by the specified business plug-in unit according to Default configuration item or according to the configuration item marked and explaining in real time, issues corresponding REST service.
8. system according to claim 7, which is characterized in that the configuration item includes at least one of or combinations thereof: Service name, port, connection number.
9. system according to claim 7, which is characterized in that further include:
Dependent status judgment module, for judging whether the specified business plug-in unit depends on restful plug-in unit, if relying on, Publication REST service then is carried out according to the corresponding configuration item of the restful plug-in unit, is otherwise issued according to default configuration item.
10. system according to any one of claim 1 to 5, which is characterized in that further include:
Resource plug expansion module, for default mapping ruler do not meet current business demand when, according to the resource plug Method in the custom interface of offer extends the mapping between the address URL and real resource path.
CN201711309851.4A 2017-12-11 2017-12-11 A kind of software architecture system Withdrawn CN109901817A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711309851.4A CN109901817A (en) 2017-12-11 2017-12-11 A kind of software architecture system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711309851.4A CN109901817A (en) 2017-12-11 2017-12-11 A kind of software architecture system

Publications (1)

Publication Number Publication Date
CN109901817A true CN109901817A (en) 2019-06-18

Family

ID=66942551

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711309851.4A Withdrawn CN109901817A (en) 2017-12-11 2017-12-11 A kind of software architecture system

Country Status (1)

Country Link
CN (1) CN109901817A (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110300025A (en) * 2019-06-28 2019-10-01 湖南御家科技有限公司 Platform service extension method and system in a kind of business
CN110764836A (en) * 2019-09-18 2020-02-07 华为技术有限公司 Method and system for realizing plug-in
CN110825358A (en) * 2019-11-22 2020-02-21 广联达科技股份有限公司 Multi-level system configuration service design method based on preorder priority matching rule

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110300025A (en) * 2019-06-28 2019-10-01 湖南御家科技有限公司 Platform service extension method and system in a kind of business
CN110764836A (en) * 2019-09-18 2020-02-07 华为技术有限公司 Method and system for realizing plug-in
US11880695B2 (en) 2019-09-18 2024-01-23 Huawei Technologies Co., Ltd. Plug-in implementation method and plug-in implementation system
CN110764836B (en) * 2019-09-18 2024-02-09 华为技术有限公司 Plug-in implementation method and plug-in implementation system
CN110825358A (en) * 2019-11-22 2020-02-21 广联达科技股份有限公司 Multi-level system configuration service design method based on preorder priority matching rule
CN110825358B (en) * 2019-11-22 2023-07-21 广联达科技股份有限公司 Multi-level system configuration service design method based on preamble priority matching rule

Similar Documents

Publication Publication Date Title
CN103309674B (en) A kind of software architecture system
CN108092884A (en) A kind of wireless access gateway system and application process
CN101447892B (en) Distributed test method, system and test server
CN101065947B (en) Web service registry and method of operation
CN101291337B (en) Grid resource management system and method
CN109901817A (en) A kind of software architecture system
CN110069380A (en) A kind of evolution of Web distributed software and monitoring method based on micro services
CN106656706A (en) Service-oriented robot open-type control system and method based on software bus
CN104883266B (en) network configuration access method and device
CN104079436A (en) Cross-device and cross-protocol EPON element management system
CN108199897A (en) A kind of OPC UA multiserver polymerizations for supporting cache management
CN105577822B (en) Caching centralized management system based on CDN node
US8769101B2 (en) Method, apparatus and system for processing composite service and replacing service and invoking service
CN107040416A (en) A kind of virtual data center visual management method based on Cairngorm frameworks
CN101582894B (en) Semantic gateway used for integration of enterprise informatization heterogeneous system
CN108255592A (en) A kind of Quartz clusters timing task processing system and method
CN103118142A (en) Load balancing method and system
CN105282191A (en) Load balancing system, controller and method
CN103716408A (en) Enterprise application integration method and system based on enterprise service bus (ESB)
CN108718244A (en) A kind of frame of reference and method for multi-service fusion
CN106027287A (en) Unified management and control platform for power distribution communication networks
CN107222575B (en) The method that OPC is communicated between realization industrial control equipment
CN111193610B (en) Intelligent monitoring data system and method based on Internet of things
CN110011984B (en) REST and RPC-based distributed cluster system and method
CN106547790A (en) A kind of relevant database service system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
WW01 Invention patent application withdrawn after publication
WW01 Invention patent application withdrawn after publication

Application publication date: 20190618