CN114153454B - Active callback scheme maintained by third party developer - Google Patents
Active callback scheme maintained by third party developer Download PDFInfo
- Publication number
- CN114153454B CN114153454B CN202111319066.3A CN202111319066A CN114153454B CN 114153454 B CN114153454 B CN 114153454B CN 202111319066 A CN202111319066 A CN 202111319066A CN 114153454 B CN114153454 B CN 114153454B
- Authority
- CN
- China
- Prior art keywords
- callback
- open platform
- merchant
- code
- service
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 claims abstract description 49
- 238000004806 packaging method and process Methods 0.000 claims description 8
- 238000007689 inspection Methods 0.000 claims description 3
- 230000001960 triggered effect Effects 0.000 claims description 3
- 238000005538 encapsulation Methods 0.000 claims 1
- 238000003032 molecular docking Methods 0.000 abstract description 6
- 238000012423 maintenance Methods 0.000 abstract description 5
- 238000000354 decomposition reaction Methods 0.000 description 2
- 239000012141 concentrate Substances 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/43—Checking; Contextual analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses an active callback scheme maintained by a third party developer, which is characterized by comprising the following steps: step S1, a callback system is built in an open platform, wherein the callback system is built by the following steps: and step S2, the merchant realizes an interface through the established callback system and uploads codes and the like. According to the invention, the enhancement points and the definition interfaces are abstracted through the open platform, and the concrete callback implementation is controlled by the merchant, so that the docking cost of the merchant and the open platform is reduced, and the development and maintenance cost of the open platform is also reduced. The open platform provides an internal service method, so that merchants only need to pay attention to use and do not need to pay attention to realization, and the development difficulty of the merchants is reduced. Meanwhile, the development platform unifies interface standards, integral business processes are standardized, the development platform is focused on services, and the docking efficiency of the development platform and multiple merchants is improved.
Description
Technical Field
The invention relates to the technical field of merchant operation platform management, in particular to an active callback scheme maintained by a third party developer.
Background
At present, after a merchant in general business triggers the business to an open platform, the open platform needs to call back different addresses according to different merchants and transmit different parameters. For example, after the order is paid, the open platform needs to call back the order payment status to the merchant a and call back the actual payment amount to the merchant B. If the control is realized by the open platform, the differentiated treatment is correspondingly increased along with the increase of merchants, the maintenance difficulty is increased in a straight line, and meanwhile, the butting cost of the merchants and the open platform is also high. There is therefore a need for a solution for proactively maintaining callback logic by merchants.
Disclosure of Invention
The invention aims to overcome the problems and provide an internal service method provided by an open platform, merchants only need to pay attention to use, and callback realizes an active callback scheme maintained by third party developers controlled by the merchants.
The aim of the invention is achieved by the following technical scheme: an active callback scheme maintained by a third party developer, comprising the following steps:
step S1, a callback system is built in an open platform, wherein the callback system is built by the following steps:
(1) And carrying out abstract decomposition on the service, embedding enhancement points into service nodes which are required to be actively called back by a user in the open platform, and defining enhancement point interfaces according to different service nodes.
(2) And providing an internal packaging method according to service requirements.
(3) The identification number is established by merchant dimension, and a merchant establishes a unique identification number appkey or APPSERCERT.
(4) And deploying a server for each merchant according to the identification number distributed by the dimension of the merchant, and binding with the unique identification number appKey or APPSERCERT of the merchant, wherein a basic java framework service is operated on the server.
And S2, the merchant realizes an interface through the established callback system and uploads a passcode.
And S3, scanning the received codes by a callback system of the open platform, and checking the scanned codes.
And S4, converting the code passing the inspection by the open platform, abstracting the code according to a hierarchical structure, writing the code into a class file and placing the class file in a java framework.
And S5, compiling, packaging and deploying the whole java framework written with the abstract code to a server.
And S6, when the service node embedded with the enhancement point is triggered, the service call active callback system is transmitted to appkey or APPSERCERT.
And S7, the active callback system checks the incoming appkey or APPSERCERT, and connects to the corresponding server after passing through.
And S8, automatically running codes uploaded by merchants by the open platform, and finally completing callback by a unified method.
The packaging method in the step (2) of establishing the callback system in the step S1 mainly comprises a method name, a packet path and a return value.
The step of verifying the scanned code in the step S3 is as follows:
① Checking whether the packet introduced into the open platform is correct or not, if not, checking that the packet does not pass; if yes, go to step ②;
② Checking whether the type and the number of the parameters of the realized interface are consistent with the interfaces defined by the enhancement points, if not, checking that the parameters do not pass; if yes, go to step ③;
③ Checking whether a calling method in a code block is in a packet path provided by an open platform, if so, checking passing; and if not, checking whether the calling method in the code block is in the current class, if not, not checking to pass, and if so, judging that the code passes the checking.
The open platform in the step S4 converts the code submitted by the merchant, and generates an abstract code including the introduced package name, class name and interface name, method name and method parameter, the code block executed in the method and the method name in the code block according to the hierarchical structure through regular matching.
When the abstracted codes are written into the java frame file according to the hierarchical structure in the step S4, a packet path of class names and packets which need to be introduced by the packet path interface are also written, and comments exposed by the method supported by the dubbo are also written for service internal registration and calling.
In the step S5, the codes in the java frame file are moved to the position under the path of the folder corresponding to the enhancement point according to the hierarchical structure, and the path is determined by the java frame used, and finally compiled and packaged, and redeployed into a server.
The step S8 is performed by a unified method to be callbackForMerchant.
Compared with the prior art, the invention has the following advantages:
(1) According to the invention, the enhancement points and the definition interfaces are abstracted through the open platform, and the concrete callback implementation is controlled by the merchant, so that the docking cost of the merchant and the open platform is reduced, and the development and maintenance cost of the open platform is also reduced.
(2) According to the invention, the internal service method is provided by the open platform, so that the merchant only needs to pay attention to use, realization is not needed to be concerned, and the development difficulty of the merchant is reduced.
(3) The invention standardizes the whole business process by unifying the interface standard for the development platform, and the development platform concentrates on the service, thereby increasing the docking efficiency of the development platform and multiple merchants.
(4) The invention is hosted on the server service through the code submitted by the merchant, reduces the maintenance cost of the merchant, simultaneously unifies the management of the development platform as the internal service, opens up the call between the service and the service, avoids the authentication problem of the call between the internal service and the external service, and makes the whole call chain form a closed loop.
Drawings
Fig. 1 is an abstract hierarchical structure diagram of the present invention.
FIG. 2 is a callback code trigger flow chart of the present invention.
Detailed Description
The present invention will be described in further detail with reference to examples, but embodiments of the present invention are not limited thereto.
Example 1
An active callback scheme maintained by a third party developer, comprising the steps of:
step S1, a callback system is built in an open platform, wherein the callback system is built by the following steps:
(1) And carrying out abstract decomposition on the service, embedding enhancement points into service nodes which are required to be actively called back by a user in the open platform, and defining enhancement point interfaces according to different service nodes.
(2) And providing an internal packaging method according to service requirements. The packaging method mainly comprises a method name, a packet path and a return value. In specific implementation, the method comprises the following steps: the method comprises the following steps: callbackForMerchant (String url, object parameters), packet path: com.open. Callback, return value: the business, wherein url is the address of the callback merchant, params is the parameter of the callback merchant, and when in use, the open platform calls back the parameter defined by the merchant to the address provided by the merchant. The method comprises the following steps: getOrderPayInfo (String orderId) packet path: com.open.order, return value: payInfo, the orderld is the order id, and when in use, the order payment information is obtained through the order id. The method comprises the following steps: getOrderInfo (String orderId) packet path: com.open.order, return value: orderInfo, orderId is order id.
(3) Identification numbers appkey or APPSERCERT are established in the merchant dimension. In particular use, a merchant establishes a unique identification number appkey or APPSERCERT.
(4) And deploying a server for each merchant according to the identification number distributed by the dimension of the merchant, and binding with the unique identification number appKey or APPSERCERT of the merchant, wherein a basic java framework service is operated on the server.
And S2, the merchant realizes an interface through the established callback system and uploads a passcode. Specifically, the merchant writes a code into the callback system through a corresponding interface according to own service requirements, and the code is a short code.
And S3, scanning the received codes by a callback system of the open platform, and checking the scanned codes. The step of checking the scanned code is as follows:
① Checking whether the packet introduced into the open platform is correct or not, if not, checking that the packet does not pass; if yes, go to step ②;
② Checking whether the type and the number of the parameters of the realized interface are consistent with the interfaces defined by the enhancement points, if not, checking that the parameters do not pass; if yes, go to step ③;
③ Checking whether a calling method in a code block is in a packet path provided by an open platform, if so, checking passing; and if not, checking whether the calling method in the code block is in the current class, if not, not checking to pass, and if so, judging that the code passes the checking.
And S4, converting the code passing the inspection by the open platform, abstracting the code according to a hierarchical structure, writing the code into a class file and placing the class file in a java framework. The open platform converts codes submitted by merchants through regular matching. As shown in FIG. 1, the code that is generated abstracted includes, in a hierarchy, an incoming package name, class name and interface name, method name and method parameters, code blocks that execute within the method, and method names in the code blocks. When the abstracted codes are written into the java frame file according to the hierarchical structure, a packet path of class names and packets which need to be introduced by the packet path interface are written, and comments exposed by the dubbo supported method are written for service internal registration and calling.
And S5, performing compiling and packing on the whole java framework written with the abstract code, and deploying the java framework to a server. Specifically, codes in the java frame file are moved to a position below a folder path corresponding to the enhancement point according to a hierarchical structure, the path is determined by the java frame, and finally, compiling and packaging are carried out, and the java frame file is deployed into a server. When the service platform is used, the code submitted by the merchant runs in the server, and the server is used as a micro-service in the open platform and can be called with other micro-services.
And S6, when the service node embedded with the enhancement point is triggered, the service call active callback system is transmitted to appkey or APPSERCERT. As shown in fig. 2.
And S7, the active callback system checks the incoming appkey or APPSERCERT, and connects to the corresponding server after passing through. As shown in fig. 2.
And S8, automatically running codes uploaded by merchants by the open platform, and finally completing callback by a unified method. Specifically, as shown in fig. 2, after the merchant finishes submitting the code, the business process triggers the enhancement point, and the open platform invokes the implementation method on the corresponding server of the merchant, and recalls the relevant information to the merchant through a unified method callbackForMerchant.
According to the invention, the enhancement points and the definition interfaces are abstracted through the open platform, and the concrete callback implementation is controlled by the merchant, so that the docking cost of the merchant and the open platform is reduced, and the development and maintenance cost of the open platform is also reduced. The open platform provides an internal service method, so that merchants only need to pay attention to use and do not need to pay attention to realization, and the development difficulty of the merchants is reduced. Meanwhile, the development platform unifies interface standards, integral business processes are standardized, the development platform is focused on services, and the docking efficiency of the development platform and multiple merchants is improved.
As described above, the present invention can be well implemented.
Claims (7)
1. An active callback scheme maintained by a third party developer, comprising the steps of:
step S1, a callback system is built in an open platform, wherein the callback system is built by the following steps:
(1) Abstract decomposing the service, embedding enhancement points into service nodes which are required to be actively called back by a user in an open platform, and defining enhancement point interfaces according to different service nodes;
(2) Providing an internal packaging method according to service requirements;
(3) Establishing an identification number according to the dimension of a merchant, and establishing a unique identification number appkey or APPSERCERT by one merchant;
(4) Deploying a server for each merchant according to the identification number distributed by the dimension of the merchant, and binding the server with the unique identification number appKey or APPSERCERT of the merchant, wherein a basic java frame service is operated on the server;
S2, the merchant realizes an interface through the established callback system and uploads a passcode;
s3, scanning the received codes by a callback system of the open platform, and checking the scanned codes;
S4, converting the code passing the inspection by the open platform, abstracting the code according to a hierarchical structure, writing a class file and placing the class file in a java framework;
S5, compiling, packaging and deploying the whole java framework written with the abstract code to a server;
Step S6, when the service node embedded with the enhancement point is triggered, the service call active callback system is transmitted to appkey or APPSERCERT;
step S7, the active callback system checks the input appkey or APPSERCERT, and connects to the corresponding server after passing through;
and S8, automatically running codes uploaded by merchants by the open platform, and finally completing callback by a unified method.
2. The active callback arrangement maintained by the third party developer according to claim 1, wherein the encapsulation method in the step (2) of establishing the callback system of step S1 mainly comprises a method name, a packet path and a return value.
3. The active callback arrangement maintained by the third party developer according to claim 1, wherein the step of verifying the scanned code in step S3 is as follows:
① Checking whether the packet introduced into the open platform is correct or not, if not, checking that the packet does not pass; if yes, go to step ②;
② Checking whether the type and the number of the parameters of the realized interface are consistent with the interfaces defined by the enhancement points, if not, checking that the parameters do not pass; if yes, go to step ③;
③ Checking whether a calling method in a code block is in a packet path provided by an open platform, if so, checking passing; and if not, checking whether the calling method in the code block is in the current class, if not, not checking to pass, and if so, judging that the code passes the checking.
4. The active callback scheme maintained by the third party developer according to claim 1, wherein the open platform in step S4 converts codes submitted by merchants through regular matching, and the generated abstract codes include, in a hierarchical structure, an introduced package name, a class name and an interface name, a method name and a method parameter, a code block executed in a method, and a method name in the code block.
5. The active callback scheme maintained by the third party developer according to claim 1, wherein when the abstract code is written into the java frame file according to the hierarchical structure in the step S4, a packet path of a class name and a packet to be introduced by the packet path interface are written, and an annotation exposed by a method supported by dubbo is written for service internal registration and call.
6. The active callback scheme maintained by the third party developer according to claim 5, wherein in step S5, the code in the java frame file is moved to the path of the folder corresponding to the enhancement point according to the hierarchical structure, and the path is determined by the used java frame, and finally compiled and packaged, and redeployed into a server.
7. The active callback arrangement maintained by the third party developer according to claim 5, wherein said step S8 is performed by a unified method of callbackForMerchant.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111319066.3A CN114153454B (en) | 2021-11-09 | 2021-11-09 | Active callback scheme maintained by third party developer |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111319066.3A CN114153454B (en) | 2021-11-09 | 2021-11-09 | Active callback scheme maintained by third party developer |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114153454A CN114153454A (en) | 2022-03-08 |
| CN114153454B true CN114153454B (en) | 2024-05-14 |
Family
ID=80459594
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111319066.3A Active CN114153454B (en) | 2021-11-09 | 2021-11-09 | Active callback scheme maintained by third party developer |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114153454B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20120081873A (en) * | 2011-01-12 | 2012-07-20 | 에스케이플래닛 주식회사 | Method for verifying mobile application and terminal using the same |
| CN105635151A (en) * | 2015-12-31 | 2016-06-01 | 深圳中兴网信科技有限公司 | Open platform access method and open platform access system |
| WO2020205962A1 (en) * | 2019-04-02 | 2020-10-08 | Virtual Hold Technology Solutions, Llc | A system and method for mobile device active callback integration |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104717132B (en) * | 2015-02-13 | 2017-10-13 | 腾讯科技（深圳）有限公司 | Message method, device and system |
-
2021
- 2021-11-09 CN CN202111319066.3A patent/CN114153454B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20120081873A (en) * | 2011-01-12 | 2012-07-20 | 에스케이플래닛 주식회사 | Method for verifying mobile application and terminal using the same |
| CN105635151A (en) * | 2015-12-31 | 2016-06-01 | 深圳中兴网信科技有限公司 | Open platform access method and open platform access system |
| WO2020205962A1 (en) * | 2019-04-02 | 2020-10-08 | Virtual Hold Technology Solutions, Llc | A system and method for mobile device active callback integration |
Non-Patent Citations (1)
| Title |
|---|
| 基于ASP.NET的B2C在线支付接口设计;郭晓菲;周廷美;江波;;现代电子技术;20090315;第32卷(第06期);第97-99页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114153454A (en) | 2022-03-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112488679B (en) | Cross-link contract analysis method of blockchain, relay chain and cross-link system | |
| CN104252339B (en) | The method and apparatus that interface layer exploitation, interface layer realize data interaction | |
| CN101826987B (en) | System and method for supporting mixed service based on integrated open network | |
| TWI767182B (en) | H5-Based Access Components and Mobile Terminals | |
| CN111290865A (en) | Service calling method and device, electronic equipment and storage medium | |
| EP2418825A1 (en) | Method and system for generating open telecommunication service based on internet | |
| CN108512748A (en) | A kind of implementation method of micro services gateway | |
| CN101645013A (en) | Plug-in type service management system and method of integrated service management platform | |
| CN111414193A (en) | Method for implementing service system based on micro-service framework and related device | |
| CN109379326B (en) | XML message rule checking method, equipment and storage medium | |
| CN101382893B (en) | On-line assembling method for component based on Web service | |
| CN113037831A (en) | Service gateway message processing method and device | |
| CN104852939A (en) | Capability interface deploying method and system | |
| Dai et al. | Automatic analysis of complex interactions in microservice systems | |
| CN103544016A (en) | Service registering configuration method and system based on JAVA reflection technology | |
| CN114510262A (en) | Interface request parameter verification method and device | |
| CN114153454B (en) | Active callback scheme maintained by third party developer | |
| CN106550026B (en) | Network communication device and method | |
| CN101765069B (en) | Value added service subscribing method, device and system | |
| CN101321178A (en) | Portal workflow engine system and its implementing method | |
| CN114416314B (en) | Service arrangement method based on API gateway | |
| CN202143092U (en) | Message processing system | |
| CN115904317A (en) | Method, device, equipment and storage medium for uniformly calling front-end interface and back-end interface | |
| CN113434118B (en) | Java platform-based hierarchical architecture system of concentrator | |
| CN114296985A (en) | Global exception handling method and platform in large-scale micro-service cluster scene |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |