CN110874250B

CN110874250B - Conversion method, system, device and storage medium of tool manufacturer and APP end

Info

Publication number: CN110874250B
Application number: CN201911142926.3A
Authority: CN
Inventors: 吴鑫; 卢晓飞; 张元元; 蔡荣
Original assignee: Hangzhou Tiankuan Technology Co ltd
Current assignee: Hangzhou Tiankuan Technology Co ltd
Priority date: 2019-11-20
Filing date: 2019-11-20
Publication date: 2023-05-02
Anticipated expiration: 2039-11-20
Also published as: CN110874250A

Abstract

The application discloses a conversion method, a conversion system, a conversion device and a conversion storage medium for a tool manufacturer and an APP end, wherein the scheme content of the application can unify and standardize the flow, and the communication cost is reduced; information sharing can be realized by integrating the application with different APP manufacturers and different tool manufacturers; and the APP service and the tool service are separated, so that the coupling property is reduced.

Description

Conversion method, system, device and storage medium of tool manufacturer and APP end

Technical Field

The present disclosure relates to the field of data conversion technologies, and in particular, to a method, a system, an apparatus, and a storage medium for converting a tool manufacturer and an APP end.

Background

There are many informationized services in the prison system at present, and many services including prisoner roll call, tool counting and the like need front-end and back-end coordination. Different APP manufacturers and different tool use manufacturers exist in different areas of prison. The same APP must be used in different versions to adapt to different vendors when each service is performed.

The main drawbacks of the prior art are:

1) One APP can only use one tool manufacturer, if a plurality of different tool manufacturers are used, a plurality of APP can be developed, the efficiency is low, and resources are wasted;

2) If the tool manufacturer updates the code module, the whole APP must be updated together, and the workload is huge;

3) Different APP manufacturers need to integrate the same tool manufacturer, and the workload is huge.

Disclosure of Invention

In order to solve the above technical problems, embodiments of the present application provide a method, a system, a device, and a storage medium for converting a tool manufacturer and an APP end.

An embodiment of the present application in a first aspect provides a method for converting a tool manufacturer and an APP end, which may include:

creating an interface file with inheritance properties, and packaging the interface file into a transfer file;

converting the transit file into a file packet in jar format by using the dex.bat file to form XX.jar and XX.SO files, packaging the XX.jar and the XX.SO files, and then placing the XX.SO files under a terminal appointed path;

the APP end configures rights in the engineering file, acquires a compressed file packet in a specified path, and decompresses the file packet;

and the APP end loads the XX.SO file, dynamically loads a file package in a tool manufacturer and jar format through a reflection mechanism, and then invokes public method contents in the file package.

Further, the creating an interface file with inheritance properties and packaging the interface file into a transfer file includes:

creating a java file XX.java which needs to inherit the interface file RFIDIMP.java; and packaging the XX.java file inherited by the RFIDIMP.java into the XX.jar file of the user.

Further, the converting the transfer file into a file packet in jar format by using the dex.bat file, forming new xx.jar and xx.so files, and placing the packaged file packet under a specified path of the terminal comprises:

and converting the JAR file of the tool manufacturer into a new JAR file by using a dex.bat file tool, packaging the JAR file, the new XX.jar and the XX.SO file of the tool manufacturer into a ZIP as a driving package, and placing the ZIP under a specified path of the terminal.

Further, the APP end obtains the compressed file package in the designated path in the engineering file configuration authority, and decompresses the file package, including:

the APP end adds network, storage, bluetooth and position authority in the configuration file of the engineering file;

the APP end decompresses the ZIP file of the driving packet in a specified path and loads the SO file of the tool manufacturer;

the APP end dynamically loads the jar files of the tool manufacturer and the scheme through a reflection mechanism.

A second aspect of the embodiments of the present application provides a conversion system between a tool manufacturer and an APP end, including:

a tool manufacturer subsystem and an APP subsystem;

the tool manufacturer subsystem is used for creating a java file of the inheritance interface file, and converting the java file into an XX. Jar package by using a conversion tool;

packaging the converted XX.jar package, SO file and jar file of the subsystem into ZIP format as driving package, and placing under the appointed path of the terminal;

the APP terminal system is used for decompressing the driving packet file under the appointed path of the terminal, loading the SO file, and dynamically loading the jar file of the tool manufacturer subsystem by utilizing the transmitting mechanism as a callable unit.

Further, the tool vendor subsystem comprises:

the creating unit is used for creating a java file XX.java which needs to inherit the interface file of the system and packaging the java file XX.jar of the subsystem;

the conversion unit converts and outputs the content in the creation unit by using the dex.bat file to form a new XX.jar file;

and the compression output unit is used for packaging the converted XX.jar file, the converted SO file and the converted Jar file of the subsystem into a format of a ZIP scheme driving package, and placing the format into a terminal appointed path.

Further, the APP terminal system includes:

the right acquisition unit is used for configuring the right in the engineering file;

the decompression reading unit is used for decompressing the ZIP file of the driving packet in the appointed path and loading the SO file of the tool manufacturer;

and the calling unit dynamically loads jar files of the tool manufacturer and the tool manufacturer subsystem by using a reflection mechanism to form calling method contents.

Further, the rights include, but are not limited to, network, storage, bluetooth, location.

In a third aspect, embodiments of the present application provide a conversion apparatus, including a memory having computer-executable instructions stored thereon, and a processor, which implements the method of the first aspect when executing the computer-executable instructions on the memory.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of the first aspect described above.

In the embodiment of the application, the scheme content of the application can unify and standardize the flow, and the communication cost is reduced; information sharing can be realized by integrating the application with different APP manufacturers and different tool manufacturers; the APP service and the tool service are separated, and the sporadic performance is reduced.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a method provided by an embodiment of the present application;

fig. 2 is a block diagram of the structure of the conversion device.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

It should be understood that the terms "comprises" and "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It is also to be understood that the terminology used in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It should be further understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".

Most files of all manufacturers have the same format content, but the manufacturer files of the RFID-two-dimensional code are basically consistent, and are not in two formats of xx.so and xx.jar.

As shown in fig. 1, the method for converting tool manufacturers and APP ends includes:

101: creating an interface file with inheritance attributes, and packaging the interface file into a transfer file.

It can be appreciated that creating a java file xx.java that needs to inherit the interface file rfidimp.java; and packaging the XX.java file inherited by the RFIDIMP.java into the XX.jar file of the user.

102: converting the transit file into a file package in jar format by using the dex.bat file to form XX.jar and XX.SO files, and packaging and then placing the files under a terminal appointed path.

It can be understood that the dex.bat file tool is utilized to convert the JAR file of the tool manufacturer into a new JAR file, the JAR file of the tool manufacturer, the new XX.jar and the XX.SO file are packaged into a ZIP as a driving package, and the ZIP is placed under a specified path of the terminal.

The steps correspond to a tool manufacturer subsystem in software, and the flow steps of the system are as follows:

(1) A java file (XX. Java) of an interface file (RFIDIMP. Java) of the scheme requiring inheritance (extensions) is created for realizing the scheme flow, and a method for realizing own needs is realized in the flow.

(2) And packaging the XX.java file inherited by the RFIDIMP.java into the XX.jar file of the user, wherein the XX.jar file is a collection of the java files.

(3) Under the build-tool/19.0.0 directory of the android SDK (other tools can be prepared by the user), the XX.jar file packed and generated in the second step is placed under the directory, and the dex.bat file is operated.

(4) All java files in the XX. Jar file package are subjected to format conversion, and as the android machine cannot identify the java files, the java files in the jar need to be converted into dex files which can be identified by the android, the command is the function, specifically, until a command window appears, dx-dex-output=dex.jar (-output= "output jar package name") xx.jar (original jar package) is input

(5) Waiting for the command to end, if the dex.jar file can be found successfully under the directory, if not, repeating the third and fourth steps until the occurrence.

(6) And packaging the converted dex.jar and SO files into a ZIP scheme driving package format, and putting the converted dex.jar and SO files into a terminal appointed path. Here, the original file SO file of the tool manufacturer can be identified by the android machine, where the file Jar in this embodiment includes the flow file (rfidimp. Java) of the method.

103: and the APP end obtains the compressed file package in the appointed path in the engineering file configuration authority and decompresses the compressed file package.

It can be understood that the APP end adds network, storage, bluetooth and position authorities in the configuration file of the engineering file.

The APP end decompresses the ZIP file of the driving packet in a specified path and loads the SO file of the tool manufacturer; the APP end dynamically loads the jar files of the tool manufacturer and the scheme through a reflection mechanism.

104: and the APP end loads the XX.SO file, dynamically loads a file package in a tool manufacturer and jar format through a reflection mechanism, and then invokes public method contents in the file package.

The steps are corresponding to an APP terminal system in software, and the flow steps of the system are as follows:

(1) The APP needs to add relevant rights of network, storage, bluetooth, position and the like in the configuration file of the engineering file.

(2) The APP goes to the path designated by the scheme, and decompresses the driving packet ZIP file.

(3) APP decompressed ZIP file loading tool manufacturer SO file

(4) APP dynamically loads jar files of tool manufacturer and scheme through reflection mechanism

(5) The APP can call the public method inside after loading the JAR file, and can call the related method according to the service requirement of the APP after the initialization step is executed.

The embodiment of the application also provides a conversion device, referring to fig. 2, and fig. 2 is a schematic block diagram of the conversion device provided by the embodiment of the application.

The embodiment of the application provides identification equipment. The object detection device 4000 comprises a processor 41 and may further comprise input means 42, output means 43 and a memory 44. The input device 42, the output device 43, the memory 44 and the processor 41 are interconnected by a bus.

The memory includes, but is not limited to, random access memory (random access memory, RAM), read-only memory (ROM), erasable programmable read-only memory (erasable programmable read only memory, EPROM), or portable read-only memory (compact disc read to only memory, CD to ROM) for the associated instructions and data.

The input means is for inputting data and/or signals and the output means is for outputting data and/or signals. The output device and the input device may be separate devices or may be a single device.

A processor may include one or more processors, including for example one or more central processing units (central processing unit, CPU), which in the case of a CPU may be a single core CPU or a multi-core CPU. The processor may also include one or more special purpose processors, which may include GPUs, FPGAs, etc., for acceleration processing.

The memory is used to store program codes and data for the network device.

The processor is used to call the program code and data in the memory to perform the steps of the method embodiments described above. Reference may be made specifically to the description of the method embodiments, and no further description is given here.

In practical applications, the motion recognition device may also include other necessary elements, including but not limited to any number of input/output devices, processors, controllers, memories, etc., and all the motion recognition devices that can implement the embodiments of the present application are within the scope of protection of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the division of the unit is merely a logic function division, and there may be another division manner when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted or not performed. The coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted across a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a read-only memory (ROM), or a random-access memory (random access memory, RAM), or a magnetic medium such as a floppy disk, a hard disk, a magnetic tape, a magnetic disk, or an optical medium such as a digital versatile disk (digital versatile disc, DVD), or a semiconductor medium such as a Solid State Disk (SSD), or the like.

The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to the specific details of the above embodiments, and various equivalent changes (such as number, shape, position, etc.) may be made to the technical solution of the present invention within the scope of the technical concept of the present invention, and these equivalent changes all belong to the protection of the present invention.

Claims

1. The conversion method between tool manufacturer and APP end is characterized by comprising the following steps:

step 101) creating an interface file with inheritance properties, and packaging the interface file into a transfer file;

step 102) converting the transit file into a file packet in jar format by using a dex.bat file to form XX.jar and XX.SO files, packaging the XX.jar and the XX.SO files, and then placing the packaged XX.SO files under a terminal appointed path;

step 103), the APP end obtains a compressed file package in a designated path in the engineering file configuration authority and decompresses the compressed file package;

step 104) the APP end loads the XX.SO file, dynamically loads a file package in a tool manufacturer and a new jar format through a reflection mechanism, and then invokes public method contents in the file package;

wherein, the step 101) includes:

creating a java file XX.java which needs to inherit the interface file RFIDIMP.java; packaging the XX.java file inherited by RFIDIMP.java into the XX.jar file of the user;

step 102) comprises: and converting the JAR file of the tool manufacturer into a new JAR file by using a dex.bat file tool, packaging the JAR file, the new XX.jar and the XX.SO file of the tool manufacturer into a ZIP as a driving package, and placing the ZIP under a specified path of the terminal.

2. The method for converting tool manufacturer and APP end according to claim 1, wherein the APP end obtains a compressed file packet in a designated path in engineering file configuration authority, and decompressing includes:

and the APP end dynamically loads the tool manufacturer and the new jar file through a reflection mechanism.

3. A tool vendor and APP end conversion system, comprising:

a tool manufacturer subsystem and an APP subsystem;

the APP terminal system is used for decompressing the driving packet file under the appointed path of the terminal, loading the SO file, and dynamically loading the jar file of the tool manufacturer subsystem by utilizing a transmitting mechanism to serve as a callable unit;

wherein the tool vendor subsystem comprises:

and the compression output unit is used for packaging the SO file, the Jar file of the subsystem and the new XX.jar file into a format of a ZIP scheme driving packet and putting the format into a terminal appointed path.

4. The tool vendor and APP end conversion system of claim 3, wherein said APP end subsystem comprises:

5. The tool vendor and APP side conversion system of claim 4, wherein said rights include but are not limited to network, storage, bluetooth, location.

6. A conversion device comprising a memory having stored thereon computer executable instructions and a processor which when executing the computer executable instructions on the memory implements the method of any of claims 1-2.

7. A computer readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, implements the method of any of the preceding claims 1-2.