CN110244990A - Application component call method, device, electronic equipment and storage medium - Google Patents
Application component call method, device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN110244990A CN110244990A CN201910356341.5A CN201910356341A CN110244990A CN 110244990 A CN110244990 A CN 110244990A CN 201910356341 A CN201910356341 A CN 201910356341A CN 110244990 A CN110244990 A CN 110244990A
- Authority
- CN
- China
- Prior art keywords
- interface
- component
- message
- application
- target
- 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
- 238000000034 method Methods 0.000 title claims abstract description 67
- 230000005540 biological transmission Effects 0.000 claims abstract description 7
- 238000004590 computer program Methods 0.000 claims description 5
- 230000008878 coupling Effects 0.000 abstract description 11
- 238000010168 coupling process Methods 0.000 abstract description 11
- 238000005859 coupling reaction Methods 0.000 abstract description 11
- 230000006870 function Effects 0.000 description 21
- 238000011161 development Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 5
- 238000010276 construction Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 235000013399 edible fruits Nutrition 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 125000000524 functional group Chemical group 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000012805 post-processing Methods 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
- G06F9/4484—Executing subprograms
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
This application discloses application component call method, device, electronic equipment and storage mediums, pass through pre-generated multiple interface containers, deposit in different types of interface message in different interface containers, it avoids different type component code level from interweaving, and then reduces application program inner couplings.Scheme is stored further combined with the specific application component, a set of specific call flow is provided, that is, when receiving the target interface information of caller transmission, by traversing each interface container, search target interface information, if finding target interface information in one of multiple interface containers, first message is returned to the caller, so that between the different engineerings of application program, while reducing code coupling, public function can be mutually called.
Description
Technical field
This application involves field of computer technology more particularly to a kind of application component call method, device, electronic equipment and
Storage medium.
Background technique
In Module Development Method technical field, functional unit and Service Component respectively represent a kind of code wrap form.Function
Component is used to a concrete function being supplied to caller, such as camera function, picture clipping function etc.；Service Component is used for will
A set of operation flow is supplied to caller.A set of operation flow generally requires to call multiple functions, such as " picture is cut out after taking pictures
And upload to application server ", wherein the function that " taking pictures ", " cutting out " and " upload " the i.e. operation flow is called.
In the service implementation method of one engineering of modularization project, usually first by relevant Service Component and functional unit
It is encapsulated into tool-class, so as to include several functional methods called in tool-class；Whole tool-class that engineering is related to again
It is stored in engineering or in a certain file directory of engineering together；When there is business demand, upper-layer service code will be direct
Reference tool category code is to call its function.Further, since an Android project all includes generally multiple engineerings, different engineerings can
It can need to call identical function or share some tool-class, therefore during actual development, if necessary to increase in the project
Add new engineering, then functional unit or Service Component needed for splitting out newly built construction from the tool-class of original engineering, to be formed
New tool-class is stored in newly built construction, and then meets the business needs of newly built construction.
In above-mentioned service implementation method, since relevant Service Component and functional group are packaged in same tool-class simultaneously
Part, and whole tool-class that engineering is related to are stored in together in engineering or in a certain file directory of engineering, therefore same work
It can be interweaved between functional unit and Service Component and tool category code and upper-layer service code under tool class, from
And code structure is caused to obscure, coupling height.
Summary of the invention
This application provides application component call method, device, electronic equipment and storage mediums, to solve existing business reality
Show in method, the problem that code structure is fuzzy, coupling is high.
In a first aspect, this application provides a kind of application component call methods, this method comprises:
The target interface information that caller is sent is received, the target interface information corresponds to target element；
By traversing pre-generated multiple interface containers, the target interface information is searched；Wherein, each interface container
For storing same type of interface message；
If finding the target interface information in one of the multiple interface container, return first message to
The caller, the first message are used to indicate the caller and call the target element.
Further, pre-generated multiple interface containers include at least:
The first interface container pre-generated according to the interface message of registered functional unit；
The second interface container pre-generated according to the interface message of registered Service Component；
The third interface container pre-generated according to application program external interface information.
Further, before the target interface information for receiving caller transmission, the method also includes:
When application program launching, the configuration information of application component is saved to receive the Active Registration of each component；It is described to answer
It include functional unit and Service Component with component；
Each registered component is instantiated according to the configuration information；
First interface container is generated according to the interface message of registered functional unit, according to the interface of registered Service Component
Information generates second interface container, and, third interface container is generated according to application program external interface information.
Further, the method also includes:
The non-active time of each component is obtained, the initial time of the non-active time is to be adjusted the component last time
Time；
If determining that the component is inactive component according to the non-active time, retain the inactive component
Configuration information, and the interface message of the inactive component is deleted from the corresponding interface container, to destroy the inactive component.
Further, the method also includes:
If not finding the target interface information in each interface container, the target element is judged
It whether is the inactive component destroyed；
If the target element is the inactive component destroyed, according to target element configuration information, example again
Change the target element, and, the interface message of the target element is added in corresponding interface container；
The first message is returned to the caller.
Further, the method also includes:
If the non-inactive component destroyed of the target element, return for notifying target element described in caller
The second message that can not be called is to caller.
Further, the method also includes: when caller receives the first message, pass through JAVA dynamic proxy
Obtain the data processed result of target element.
Second aspect, this application provides a kind of application component managing devices, comprising:
Component register module, for storing the configuration information of application component, to complete the Active Registration of application component；It is described
Application component includes functional unit and Service Component；
Interface storage module；The interface storage module includes multiple pre-generated interface containers, wherein each interface
Container is for storing same type of interface message；
Management module, for receiving the target interface information of caller transmission；The target interface information corresponds to target
Component；
And by traversing the multiple interface container, search the target interface information；
If finding the target interface information in one of the multiple interface container, first message is returned to institute
Caller is stated, the first message is used to indicate the caller and calls the target element.
Further, pre-generated multiple interface containers include at least:
The first interface container pre-generated according to the interface message of registered functional unit；
The second interface container pre-generated according to the interface message of registered Service Component；
The third interface container pre-generated according to application program external interface information.
Further, the management module is also used to:
Each registered component is instantiated according to the configuration information；
First interface container is generated according to the interface message of registered functional unit, according to the interface of registered Service Component
Information generates second interface container, and, third interface container is generated according to application program external interface information.
Further, the management module is also used to:
The non-active time of each component is obtained, the initial time of the non-active time is to be adjusted the component last time
Time；
If determining that the component is inactive component according to the non-active time, retain the inactive component
Configuration information, and the interface message of the inactive component is deleted from the corresponding interface container, to destroy the inactive component.
Further, the management module is also used to:
If not finding the target interface information in each interface container, the target element is judged
It whether is the inactive component destroyed；
If the target element is the inactive component destroyed, according to target element configuration information, example again
Change the target element, and, the interface message of the target element is added in corresponding interface container；
The first message is returned to the caller.
Further, the management module is also used to:
If the non-inactive component destroyed of the target element, return for notifying target element described in caller
The second message that can not be called is to caller.
The third aspect, this application provides a kind of electronic equipment, comprising:
Memory, for storing program instruction；
Processor, for calling and executing the program instruction in the memory, to realize application described in first aspect
Component call method.
Fourth aspect is stored with computer program in the storage medium this application provides a kind of storage medium, when answering
When executing the computer program at least one processor of assembly management device, application component managing device executes first party
Application component call method described in face.
From the above technical scheme, application component call method provided by the present application, device, electronic equipment and storage are situated between
Matter is deposited in different types of interface message in different interface containers, is avoided by pre-generated multiple interface containers
Different type component code level interweaves, and then reduces application program inner couplings.It is specifically answered further combined with this
Scheme is stored with component, a set of specific call flow is provided, that is, when receiving the target interface information of caller transmission,
By traversing each interface container, target interface information is searched, is connect if finding target in one of multiple interface containers
Message breath then returns to first message to the caller, so as to reduce the same of code coupling between the different engineerings of application program
When, it can mutually call public function.
Detailed description of the invention
In order to illustrate more clearly of the technical solution of the application, letter will be made to attached drawing needed in the embodiment below
Singly introduce, it should be apparent that, for those of ordinary skills, without any creative labor,
It is also possible to obtain other drawings based on these drawings.
Fig. 1 is that the application application component call method realizes schematic diagram of a scenario；
Fig. 2 is one embodiment flow chart of the application application component call method；
Fig. 3 is an exemplary realization scene figure of the embodiment of the present application；
Fig. 4 is another embodiment flow chart of the application application component call method；
Fig. 5 is another embodiment flow chart of the application application component call method；
Fig. 6 is one embodiment schematic diagram of the application application component managing device；
Fig. 7 is the hardware structural diagram of electronic equipment provided by the embodiments of the present application.
Specific embodiment
In order to make those skilled in the art better understand the technical solutions in the application, below in conjunction with the application reality
The attached drawing in example is applied, the technical scheme in the embodiment of the application is clearly and completely described, it is clear that described implementation
Example is merely a part but not all of the embodiments of the present application.Based on the embodiment in the application, this field is common
The application protection all should belong in technical staff's every other embodiment obtained without making creative work
Range.
In existing modularization project service implementation method, since relevant business is packaged in same tool-class simultaneously
Component and functional unit, and whole tool-class for being related to of engineering are stored in engineering together or a certain file directory of engineering
In, therefore can be sent out between the functional unit and Service Component and tool category code and upper-layer service code under same tool-class
Life is interweaved, to cause code structure to obscure, coupling height.
In order to solve the above-mentioned technical problem, the application provides a kind of application component call method and application component management dress
It sets, refering to fig. 1, basic ideas are: application component managing device being made to run on application program, be implemented in the application method and answer
With assembly management device.Wherein, when application program launching, the component register module in application component managing device receives application
The Active Registration of component.Multiple interface containers are provided by interface storage module, separate different types of interface message
Storage, avoids different type component code level from interweaving, and then reduces application program inner couplings.Pass through management module
The application method is executed, to provide the call flow of a set of fixation, between making the different engineerings of application program, is reducing code coupling
While, it can mutually call public function.
It, below will be right in order to make those skilled in the art further appreciate that the thinking and implementation of technical scheme
Application component call method provided by the present application is discussed in detail.
Fig. 2 is one embodiment flow chart of the application application component call method.Wherein, application component generally comprises function
Energy component and Service Component, functional unit can provide a concrete function for caller, and Service Component can mention for caller
For a set of operation flow.The realization of the provided operation flow of Service Component generally requires to call multiple function realized by functional unit
Energy.In addition, in order to realize that all functional unit and Service Component are consistent operation standard, the convenient management to assembly function
And test, in the application method, all functional units and Service Component are followed in the calling service development pre-defined
Specification.As shown in Fig. 2, this method may include:
Step 110, the target interface information that caller is sent is received, the target interface information corresponds to target element.
Caller refers to the main body with calling demand, can be the Service Component in same application, is also possible to
Other applications.
Interface message includes at least the identity (Identification, abbreviation ID) of an application component, generally deposits
In Chu Qi configuration information.When caller needs to call some assembly function, it should first know the interface of wanted invocation component
Information.The target element that the caller assembly function to be called i.e. step 110 is related to, identity, that is, step of target element
The 110 target interface information being related to.
The present embodiment passes through the management module of application component managing device, provides a unification to the calling service of inter-module
Target interface information is sent to management module, by management module when caller needs to call a certain function or process by process
Directly search target element example.
Step 120, by traversing pre-generated multiple interface containers, the target interface information is searched.Wherein, each
Interface container is for storing same type of interface message.
It is external that the type of interface message includes at least functional unit interface message, Service Component interface message and application program
Interface message.Wherein, application program external interface refers to the calling interface for completing the external service call of application component.
Based on this, the multiple interface containers of the application are included at least: according to the pre- Mr. of the interface message of registered functional unit
At first interface container, according to the interface message of registered Service Component pre-generate second interface container and, according to
The pre-generated third interface container of application program external interface information.These interface containers can receive calling in application component
Component instance is pre-generated before and is added in management module.
In some embodiments, when application program launching, application component managing device starts therewith, and then multiple interfaces hold
Device can generate as steps described below:
Firstly, submitting configuration information to application component managing device, component register module is by the configuration information of each component
It saves, it is meant that receive the Active Registration of each component, so as to caller calling.
As shown in figure 3, configuration information can actively be submitted to component by a public registration interface predetermined
Managing device.It may include the multinomial information of application component in configuration information, such as the identity of component interface, binary library generation
Code storage position etc..
In the prior art, the configuration information for providing the component called can be generally stored in underlying registry, works as needs
When calling, then relevant configuration information is read from underlying registry.Compared with prior art, configuration information is stored in by the application
In component register module, without reading from underlying registry, and then the level of service call is reduced, while convenient for application
Assembly management device is managed collectively the calling between component.
Then each registered component is instantiated further according to the configuration information of preservation, that is, creates the reality of each registered component
Example.First interface container is finally generated according to the interface message of registered functional unit, according to the interface of registered Service Component
Information generates second interface container, and, third interface container is generated according to application program external interface information.
With continued reference to Fig. 3, registered application component example can by a public loading interface predetermined,
It is loaded into corresponding interface container.
It should be noted that the quantity of first interface container, second interface container or third interface container can be one,
Be also possible to it is multiple, when to be multiple, due to its storage interface message type it is identical, the application is referred to as first
Interface container, second interface container or third interface container.
It, can be to avoid the functional unit and business under same tool-class by storing functional unit and Service Component respectively
Component, and, it is interweaved between tool category code and upper-layer service code, is sufficiently decoupled in code level, make service layer
Sharpness of border strengthens the encapsulation and reusability of every kind of component.
In addition, in existing service implementation method, in the case where more people develop simultaneously, due to may between different engineerings
It calls identical function or shares some tool-class, therefore developer not only needs to be concerned about the business realizing of oneself, it is also necessary to
Synchronize the modification content of other developers in time, and if necessary to increase new engineering in the project, then it can be from original work
Functional unit needed for the tool-class of journey splits out newly built construction or Service Component to cause the waste of development cost, and are developed
It is inefficient.
Based on the application method, functional unit and Service Component can individually be developed, therefore multiple open can be made
Hair personnel's concurrent development, also, since the call flow of component is followed in calling service development specification predetermined, it is every
One developer only needs to be concerned about the business realizing of institute's developer component, further increases development efficiency.In addition, according to unification
The component for calling service development specification to complete facilitates assembly transfer and the upgrading in later period, when needing newly-increased or change component engineering,
Without splitting and extracting from original engineering, the development time is saved, development cost is reduced.
Step 130, if finding the target interface information in one of the multiple interface container, is returned
One message gives the caller, and the first message is used to indicate the caller and calls the target element.
Each interface message stored in each interface container is traversed, by itself and target interface information comparison, if
Match, then finds target interface information.At this point, returning to first message indicates that caller can be with invocation target component to caller
Example.
When caller receives first message, the data processing knot of target element will be obtained by JAVA dynamic proxy
Fruit.
Proxy mode is common JAVA design pattern, it is characterized in that proxy class and commission class have same interface, is acted on behalf of
Class, which is mainly responsible for, to be pre-processed message, filter message for commission class, forwards the message to commission class and post-processing message etc..
Usually there will be incidence relation between proxy class and commission class, the object of a proxy class entrusts the object of class to be associated with one,
Object of proxy class itself does not realize service really, but by calling the correlation technique of the object of commission class, to provide spy
Fixed service.
Static agent be source code is automatically generated by programmer's creation or particular tool, that is, in compiling just incited somebody to action
Interface, proxied class, proxy class etc. are decided.Before program operation, the class file of proxy class has just been generated.
The agent way that proxy class is created when program is run is known as dynamic proxy.Compared with static agent, proxy class
It is not but " instruction " dynamic generation according to us in JAVA code at runtime defined in the JAVA code,
It is advantageous that easily the function of proxy class can be carried out unified processing, and do not have to modify the side in each proxy class
Method.
In the software product at present using Android Module Development Method technology, usually there is application program launching speed
Slowly, the problems such as EMS memory occupation is more, CPU usage is high, this is because it is loaded with excessive component when application program launching, and it is every
A component can occupy certain memory headroom and cpu resource again, can't bear so as to cause entire application program is too fat to move.
In order to solve above-mentioned technical problem simultaneously, the application mode embodiment can also include destroying registered component instance
The step of, i.e., in above-mentioned steps 110 to the following step for executing execution between step 130, thus releasing memory and cpu resource.
In step 410, the non-active time of each component is obtained.
Wherein, the non-active time of component, which refers to, originates from the last time called time to one section of current time termination
Time, for characterizing the being of little use property of component.
At step 420, judge whether the non-active time of each component is greater than the preset component time-to-live.
For example, application component managing device presets a component time-to-live, and record nearest the one of each component interface
The secondary response time as the component last time be called time to obtain non-active time, according to non-active time with it is preset
The size relation of component time-to-live determines whether the component is inactive component.
In step 430, the component for determining that non-active time is greater than the component time-to-live is inactive component, and reservation is not lived
Jump the configuration information of component, and deletes from the corresponding interface container the interface message of the inactive component, with destroy it is described not
Enliven component.
Specifically, if inactive component is functional unit, its interface message is deleted from first interface container,
If inactive component is Service Component, its interface message is deleted from second interface container, with releasing memory space and
CPU is occupied.
In order to avoid target element example is the component instance that managing device has been destroyed, the application component call method it is another
One embodiment includes the following steps:
Step 510, the target interface information that caller is sent is received, the target interface information corresponds to target element.
Step 520, by traversing pre-generated multiple interface containers, the target interface information is searched；Wherein, each
Interface container is for storing same type of interface message.
Step 530, if not finding the target interface information in each interface container, judge the target
Whether component is the inactive component destroyed.
Step 540, if the target element is the inactive component destroyed, according to target element configuration information,
Again target element is instantiated, and, the interface message of target element is added in corresponding interface container.
Step 550, the first message is returned to the caller.
Step 560, it if the non-inactive component destroyed of the target element, returns for notifying caller target
The second message that component instance can not call is to caller.
Using the present embodiment method, can to avoid destroying the phenomenon that inactive component instance cause funcall to fail, into
And improve the integrity of the application application component call method.
As seen from the above embodiment, application component call method provided in this embodiment multiple is connect by pre-generated
Mouth container, deposits in different types of interface message in different interface containers, and different type component code level is avoided to send out
It is raw to interweave, and then reduce application program inner couplings.Scheme is stored further combined with the specific application component, is provided a set of
Specific call flow, that is, when receiving the target interface information of caller transmission, by traversing each interface container, look into
Look for target interface information, if finding target interface information in one of multiple interface containers, return first message to
The caller, so as to while reducing code coupling, can mutually call public function between the different engineerings of application program
Energy.
The embodiment of the present application also provides a kind of application component call method applied to caller side, specifically can wrap
It includes:
Step 610, target interface information is sent to application component managing device, the target interface information corresponds to target
Component instance.
Step 620, when being used to indicate of receiving that the application component managing device sends calls the target element real
When the first message of example, the data processed result of the target element example is obtained by JAVA dynamic proxy；Wherein, described
One message is by application component managing device according to the lookup knot of the traversal lookup target interface information in multiple interface containers
Fruit generates, each interface container stores a type of interface message.
Fig. 6 is one embodiment schematic diagram of the application application component managing device.As shown in fig. 6, the application component pipe
Managing device includes: component register module U610, for storing the configuration information of application component, to complete the active note of application component
Volume；The application component includes functional unit and Service Component；Interface storage module U620；The interface storage module includes more
A pre-generated interface container, wherein each interface container is for storing same type of interface message；Management module
U630, for receiving the target interface information of caller transmission；The target interface information corresponds to target element example；With
And by traversing the multiple interface container, search the target interface information；If in one of the multiple interface container
The target interface information is found, then returns to first message to the caller, the first message is used to indicate the tune
User calls the target element example.
In further embodiments, management module U630 is also used to execute the application Fig. 4 and method and step shown in fig. 5,
Specific implementation can be found in above method embodiment, and details are not described herein again.
Fig. 7 is the hardware structural diagram of electronic equipment provided in an embodiment of the present invention.As shown in fig. 7, the electronic equipment,
It may include: memory 710, for storing program instruction；Processor 720, for calling and executing the journey in the memory
Sequence instruction, to realize above-mentioned application component call method.
In the present embodiment, memory 710 can be connected with processor 720 by bus or other modes.Processor can be
General processor, such as central processing unit, digital signal processor, specific integrated circuit, or be configured to implement the present invention
One or more integrated circuits of embodiment.Memory may include volatile memory, such as random access memory；Storage
Device also may include nonvolatile memory, such as read-only memory, flash memory, hard disk or solid state hard disk.
In the specific implementation, the present invention also provides a kind of computer storage mediums, wherein the computer storage medium can store
There is calculation procedure, when at least one processor of application component managing device executes the computer program, application component pipe
Reason device some or all of executes in each embodiment of the application application component call method step.The storage medium can
For magnetic disk, CD, read-only memory (English: read-only memory, abbreviation: ROM) or random access memory (English
Text: random access memory, referred to as: RAM) etc..
It is required that those skilled in the art can be understood that the technology in the embodiment of the present invention can add by software
The mode of general hardware platform realize.Based on this understanding, the technical solution in the embodiment of the present invention substantially or
Say that the part that contributes to existing technology can be embodied in the form of software products, which can deposit
Storage is in storage medium, such as ROM/RAM, magnetic disk, CD, including some instructions are used so that computer equipment (can be with
It is personal computer, server or the network equipment etc.) execute certain part institutes of each embodiment of the present invention or embodiment
The method stated.
It should be appreciated that specification and claims and term " first " in above-mentioned attached drawing in the application, " second ",
" third " etc. is to be used to distinguish similar objects, without being used to describe a particular order or precedence order.It should be understood that in this way
The data used are interchangeable under appropriate circumstances, for example, can according to the embodiment of the present application illustrate or describe in provide those with
Outer sequence is implemented.
Term " module " used herein refers to hardware that is any known or developing later, software, firmware, artificial
The combination of intelligence, fuzzy logic or hardware or/and software code, is able to carry out function relevant to the element.
Same and similar part may refer to each other between each embodiment in this specification.Especially for application component
For managing device and electronic equipment embodiment, since it is substantially similar to the method embodiment, so being described relatively simple, phase
Place is closed referring to the explanation in embodiment of the method.
Invention described above embodiment is not intended to limit the scope of the present invention..
Claims (15)
1. a kind of application component call method characterized by comprising
The target interface information that caller is sent is received, the target interface information corresponds to target element；
By traversing pre-generated multiple interface containers, the target interface information is searched；Wherein, each interface container is used for
Store same type of interface message；
If finding the target interface information in one of the multiple interface container, first message is returned to described
Caller, the first message are used to indicate the caller and call the target element.
2. the method according to claim 1, wherein pre-generated multiple interface containers include at least:
The first interface container pre-generated according to the interface message of registered functional unit；
The second interface container pre-generated according to the interface message of registered Service Component；
The third interface container pre-generated according to application program external interface information.
3. according to the method described in claim 2, it is characterized in that, it is described receive caller send target interface information it
Before, the method also includes:
When application program launching, the configuration information of application component is saved to receive the Active Registration of each component；The application group
Part includes functional unit and Service Component；
Each registered component is instantiated according to the configuration information；
First interface container is generated according to the interface message of registered functional unit, according to the interface message of registered Service Component
Second interface container is generated, and, third interface container is generated according to application program external interface information.
4. method according to claim 1-3, which is characterized in that the method also includes:
The non-active time of each component is obtained, the initial time of the non-active time is what the component last time was called
Time；
If determining that the component is inactive component according to the non-active time, retain the configuration of the inactive component
Information, and the interface message of the inactive component is deleted from the corresponding interface container, to destroy the inactive component.
5. the method according to claim 1, wherein the method also includes:
If not finding the target interface information in each interface container, whether the target element is judged
For the inactive component destroyed；
If the target element is the inactive component destroyed, according to target element configuration information, institute is instantiated again
Target element is stated, and, the interface message of the target element is added in corresponding interface container；
The first message is returned to the caller.
6. according to the method described in claim 5, it is characterized in that, the method also includes:
If the non-inactive component destroyed of the target element, return for notifying that target element described in caller can not
The second message of calling is to caller.
7. the method according to claim 1, wherein the method also includes: when caller receives described
When one message, the data processed result of target element is obtained by JAVA dynamic proxy.
8. a kind of application component managing device characterized by comprising
Component register module, for storing the configuration information of application component, to complete the Active Registration of application component；The application
Component includes functional unit and Service Component；
Interface storage module；The interface storage module includes multiple pre-generated interface containers, wherein each interface container
For storing same type of interface message；
Management module, for receiving the target interface information of caller transmission；The target interface information corresponds to target element；
And by traversing the multiple interface container, search the target interface information；
If finding the target interface information in one of the multiple interface container, first message is returned to the tune
User, the first message are used to indicate the caller and call the target element.
9. application component managing device according to claim 8, which is characterized in that pre-generated multiple interfaces hold
Device includes at least:
The first interface container pre-generated according to the interface message of registered functional unit；
The second interface container pre-generated according to the interface message of registered Service Component；
The third interface container pre-generated according to application program external interface information.
10. application component managing device according to claim 9, which is characterized in that the management module is also used to:
Each registered component is instantiated according to the configuration information；
First interface container is generated according to the interface message of registered functional unit, according to the interface message of registered Service Component
Second interface container is generated, and, third interface container is generated according to application program external interface information.
11. according to application component managing device described in claim 8-10, which is characterized in that the management module is also used to:
The non-active time of each component is obtained, the initial time of the non-active time is what the component last time was called
Time；
If determining that the component is inactive component according to the non-active time, retain the configuration of the inactive component
Information, and the interface message of the inactive component is deleted from the corresponding interface container, to destroy the inactive component.
12. application component managing device according to claim 8, which is characterized in that the management module is also used to:
If not finding the target interface information in each interface container, whether the target element is judged
For the inactive component destroyed；
If the target element is the inactive component destroyed, according to target element configuration information, institute is instantiated again
Target element is stated, and, the interface message of the target element is added in corresponding interface container；
The first message is returned to the caller.
13. application component managing device according to claim 12, which is characterized in that the management module is also used to:
If the non-inactive component destroyed of the target element, return for notifying that target element described in caller can not
The second message of calling is to caller.
14. a kind of electronic equipment characterized by comprising
Memory, for storing program instruction；
Processor, for calling and executing the program instruction in the memory, to realize that claim 1-7 is described in any item
Application component call method.
15. a kind of storage medium, which is characterized in that computer program is stored in the storage medium, when application component management
When at least one processor of device executes the computer program, application component managing device perform claim requires 1-7 any
Application component call method described in.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910356341.5A CN110244990A (en) | 2019-04-29 | 2019-04-29 | Application component call method, device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910356341.5A CN110244990A (en) | 2019-04-29 | 2019-04-29 | Application component call method, device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110244990A true CN110244990A (en) | 2019-09-17 |
Family
ID=67883488
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910356341.5A Pending CN110244990A (en) | 2019-04-29 | 2019-04-29 | Application component call method, device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110244990A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110825448A (en) * | 2019-09-18 | 2020-02-21 | 五八有限公司 | Method, device, electronic equipment and storage medium for realizing mutual calling of multiple service modules |
| CN111131497A (en) * | 2019-12-31 | 2020-05-08 | 五八有限公司 | File transmission method and device, electronic equipment and storage medium |
| CN111459475A (en) * | 2020-03-30 | 2020-07-28 | 北京三快在线科技有限公司 | Interface calling method, interface docking configuration method, device, equipment and medium |
| WO2021169623A1 (en) * | 2020-02-29 | 2021-09-02 | 苏州浪潮智能科技有限公司 | Service processing method and apparatus, and electronic device and storage medium |
| CN113778422A (en) * | 2021-08-04 | 2021-12-10 | 山东浪潮通软信息科技有限公司 | Method and device for publishing mobile application |
| CN114168227A (en) * | 2021-12-10 | 2022-03-11 | 掌阅科技股份有限公司 | Program call processing method, electronic device and computer storage medium |
| CN114461291A (en) * | 2020-10-22 | 2022-05-10 | 北京国双科技有限公司 | Application program component calling method and device, electronic equipment and storage medium |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1805431A (en) * | 2005-01-12 | 2006-07-19 | 北京航空航天大学 | Web service processing system for remote portal components |
| CN1959631A (en) * | 2005-11-04 | 2007-05-09 | 上海启明软件股份有限公司 | Self-contained technology for installing application software based on ITRON |
| CN101266542A (en) * | 2008-02-01 | 2008-09-17 | 中国建设银行股份有限公司 | Method and device for loading component in container |
| US20120233591A1 (en) * | 2011-03-11 | 2012-09-13 | Sivakumar Melapannai Thyagarajan | Type-safe Dependency Injection of Services into Enterprise Components |
| CN102681854A (en) * | 2012-05-18 | 2012-09-19 | 华为技术有限公司 | Service execution method, server and computer system |
| CN104915185A (en) * | 2014-03-11 | 2015-09-16 | 腾讯科技（深圳）有限公司 | Coupling processing method for program components and related device |
| CN105975261A (en) * | 2016-04-28 | 2016-09-28 | 南开大学 | Uniform interface calling oriented runtime system and running method |
| CN106250165A (en) * | 2016-06-12 | 2016-12-21 | 杭州无量网络科技有限公司 | Application component management method and system |
| CN107733922A (en) * | 2017-11-20 | 2018-02-23 | 百度在线网络技术（北京）有限公司 | Method and apparatus for calling service |
| EP3396543A1 (en) * | 2017-04-26 | 2018-10-31 | Nokia Solutions and Networks Oy | Method to allocate/deallocate resources on a platform, platform and computer readable medium |
| CN108958796A (en) * | 2017-05-23 | 2018-12-07 | 阿里巴巴集团控股有限公司 | service request processing method and device, service request processing system |
| CN109359147A (en) * | 2018-09-27 | 2019-02-19 | 北京京东尚科信息技术有限公司 | Service Component processing method, component server and system |
-
2019
- 2019-04-29 CN CN201910356341.5A patent/CN110244990A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1805431A (en) * | 2005-01-12 | 2006-07-19 | 北京航空航天大学 | Web service processing system for remote portal components |
| CN1959631A (en) * | 2005-11-04 | 2007-05-09 | 上海启明软件股份有限公司 | Self-contained technology for installing application software based on ITRON |
| CN101266542A (en) * | 2008-02-01 | 2008-09-17 | 中国建设银行股份有限公司 | Method and device for loading component in container |
| US20120233591A1 (en) * | 2011-03-11 | 2012-09-13 | Sivakumar Melapannai Thyagarajan | Type-safe Dependency Injection of Services into Enterprise Components |
| CN102681854A (en) * | 2012-05-18 | 2012-09-19 | 华为技术有限公司 | Service execution method, server and computer system |
| CN104915185A (en) * | 2014-03-11 | 2015-09-16 | 腾讯科技（深圳）有限公司 | Coupling processing method for program components and related device |
| CN105975261A (en) * | 2016-04-28 | 2016-09-28 | 南开大学 | Uniform interface calling oriented runtime system and running method |
| CN106250165A (en) * | 2016-06-12 | 2016-12-21 | 杭州无量网络科技有限公司 | Application component management method and system |
| EP3396543A1 (en) * | 2017-04-26 | 2018-10-31 | Nokia Solutions and Networks Oy | Method to allocate/deallocate resources on a platform, platform and computer readable medium |
| CN108958796A (en) * | 2017-05-23 | 2018-12-07 | 阿里巴巴集团控股有限公司 | service request processing method and device, service request processing system |
| CN107733922A (en) * | 2017-11-20 | 2018-02-23 | 百度在线网络技术（北京）有限公司 | Method and apparatus for calling service |
| CN109359147A (en) * | 2018-09-27 | 2019-02-19 | 北京京东尚科信息技术有限公司 | Service Component processing method, component server and system |
Non-Patent Citations (2)
| Title |
|---|
| 孙旭东等: "油气勘探数据管理与集成应用", 电子科技大学出版社, pages: 209 - 219 * |
| 苟虹雨: "基于Android平台的组件化即时通信系统的设计与实现", 《中国优秀硕士学位论文全文数据库信息科技辑》, 15 March 2018 (2018-03-15) * |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110825448A (en) * | 2019-09-18 | 2020-02-21 | 五八有限公司 | Method, device, electronic equipment and storage medium for realizing mutual calling of multiple service modules |
| CN110825448B (en) * | 2019-09-18 | 2023-10-27 | 五八有限公司 | Method, device, electronic equipment and storage medium for realizing multi-service module mutual calling |
| CN111131497A (en) * | 2019-12-31 | 2020-05-08 | 五八有限公司 | File transmission method and device, electronic equipment and storage medium |
| CN111131497B (en) * | 2019-12-31 | 2022-08-26 | 五八有限公司 | File transmission method and device, electronic equipment and storage medium |
| WO2021169623A1 (en) * | 2020-02-29 | 2021-09-02 | 苏州浪潮智能科技有限公司 | Service processing method and apparatus, and electronic device and storage medium |
| US11704139B2 (en) | 2020-02-29 | 2023-07-18 | Inspur Suzhou Intelligent Technology Co., Ltd. | Service processing method and apparatus, electronic device, and storage medium |
| CN111459475A (en) * | 2020-03-30 | 2020-07-28 | 北京三快在线科技有限公司 | Interface calling method, interface docking configuration method, device, equipment and medium |
| CN111459475B (en) * | 2020-03-30 | 2023-05-16 | 北京三快在线科技有限公司 | Interface calling method, interface docking configuration method, device, equipment and medium |
| CN114461291A (en) * | 2020-10-22 | 2022-05-10 | 北京国双科技有限公司 | Application program component calling method and device, electronic equipment and storage medium |
| CN113778422A (en) * | 2021-08-04 | 2021-12-10 | 山东浪潮通软信息科技有限公司 | Method and device for publishing mobile application |
| CN114168227A (en) * | 2021-12-10 | 2022-03-11 | 掌阅科技股份有限公司 | Program call processing method, electronic device and computer storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110244990A (en) | Application component call method, device, electronic equipment and storage medium | |
| CN110162470B (en) | Block chain testing method and device | |
| US10585785B2 (en) | Preservation of modifications after overlay removal from a container | |
| CN110569108B (en) | Method for creating execution environment of mini-game virtual machine and related product | |
| CN108616599A (en) | Application service registration, newer method and device | |
| CN112463211A (en) | System architecture transformation method compatible with multiple development architectures and system architecture | |
| TW202040386A (en) | Storage and execution method and device of intelligent contract in block chain and electronic device | |
| CN109032820A (en) | The compatible processing method and processing device of application version | |
| CN104731622A (en) | Application program loading method and device and mobile terminal | |
| CN114020444B (en) | Calling system and method for resource service application in enterprise digital middle station | |
| CN109032685A (en) | A kind of method and terminal accelerating Android system starting | |
| CN110083366B (en) | Application running environment generation method and device, computing equipment and storage medium | |
| CN108664343A (en) | A kind of stateful call method and device of micro services | |
| CN112905263A (en) | Loading method and device of custom component, electronic equipment and storage medium | |
| CN110673827B (en) | Resource calling method and device based on android system and electronic equipment | |
| CN107463638A (en) | File sharing method and equipment between offline virtual machine | |
| CN113835748B (en) | Packaging method, system and readable medium for application program based on HTML5 | |
| CN110955415A (en) | Method for adapting projection multi-platform service | |
| US9183001B2 (en) | Simulation of static members and parameterized constructors on an interface-based API | |
| CN102184105A (en) | Data processing method based on modularity and data center system | |
| CN114880073A (en) | Cloud application engine deployment method, device, equipment and storage medium for shielding Web framework for user | |
| CN114610381A (en) | Method, device, equipment and storage medium for calling method service | |
| CN114064678A (en) | Event data processing method and device and terminal equipment | |
| CN108845953B (en) | Interface testing method and device | |
| CN113867776A (en) | Method and device for publishing middle station application, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for 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: 20190917 |