CN102393845B - Shared library management method and system - Google Patents
Shared library management method and system Download PDFInfo
- Publication number
- CN102393845B CN102393845B CN 201110182142 CN201110182142A CN102393845B CN 102393845 B CN102393845 B CN 102393845B CN 201110182142 CN201110182142 CN 201110182142 CN 201110182142 A CN201110182142 A CN 201110182142A CN 102393845 B CN102393845 B CN 102393845B
- Authority
- CN
- China
- Prior art keywords
- shared library
- version
- classification
- information
- jdk
- 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
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a shared library management method and system. The method comprises the following steps of: uploading files of JDKs (java development kits) and shared libraries to a version control server; storing the description information of the JDKs and the description information and dependency information of the shared libraries into an information database; when a designated JDK is required to be acquired, searching the corresponding description information of the designated JDK from the information database firstly, and then acquiring the files of the designated JDK from the version control server according to the description information; and when a designated shared library is required to be acquired, searching the corresponding description information and dependency information of the shared library from the information database firstly, then acquiring the files of the designated shared library from the version control server according to the description information of the shared library, and acquiring files of other packets relied by the designated shared library according to the dependency information of the shared library. According to the technical scheme of the invention, JDKs and shared libraries can be managed reasonably, so that the JDKs and the shared libraries can be rapidly and consistently quoted by other services.
Description
Technical field
The present invention relates to field of computer technology, particularly relate to a kind of shared library management method and system.
Background technology
The Internet era, the consumer improves day by day to the demand of Virtual Service, the service provider is to attract the consumer to the capability of fast response of new service, improves the important indicator of customer loyalty.
But in the process of fast Development, rapid deployment service, can run into following problem: increasing third party library will be introduced into, the introducing mode of past ad-hoc causes the third party to wrap in and introduces the upper problems such as introducing, incompatible introducing, inconsistent introducing that repeat that exist; These problems are that the deployment of service from now on causes potential problem; Therefore how reasonably, correctly, consistance using and to manage third party library in full company, is company's major issue that faces under development.In addition, for increasing Service Source; How to effectively utilize, multiplexing existing service, be to play a key effect to promoting the utilization factor of corporate resource, reducing costs.
Summary of the invention
The invention provides a kind of shared library management method, the method can reasonably be managed JDK and shared library, in order to can be served fast, as one man quote by other.
The present invention also provides a kind of shared library management system, and this system can reasonably manage JDK and shared library, in order to can be served fast, as one man quote by other.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention discloses a kind of shared library management method, the method comprises:
With the File Upload of the JDK assigned address to version control server, under the deposit position of the corresponding shared library classification with the File Upload of shared library in the version control server;
The descriptor of JDK is saved in information database; Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server;
Shared library descriptor and shared library Dependency Specification are saved in information database;
The descriptor of described shared library comprises: the fileinfo that the shared library information of the classification information of shared library, shared library information, concrete version, the shared library of concrete version comprise, the attribute information of concrete version shared library; Wherein comprise the positional information of shared library in version control server in the classification information of shared library;
The Dependency Specification of described shared library comprises: the storehouse of the shared library that the storehouse of shared library indicates and relied on indicates;
When needs obtain appointment JDK, arrive first and search corresponding descriptor in information database, obtain the file of this appointment JDK from version control server according to descriptor;
When needs obtain the appointment shared library, arrive first and search corresponding shared library descriptor and shared library Dependency Specification in information database, obtain the file of this appointment shared library according to the shared library descriptor from version control server, obtain the file of other bag that is relied on by this appointment shared library according to the shared library Dependency Specification.
The present invention also provides a kind of shared library management system, and this system comprises: version control server, information database and Access Management Access center, wherein:
Version control server is used for preserving JDK at the assigned address of self, and category is preserved shared library in the assigned address of self;
Information database, the descriptor that is used for preserving JDK, and the Dependency Specification of the descriptor of shared library and shared library;
Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server; The descriptor of described shared library comprises: the fileinfo that the shared library information of the classification information of shared library, shared library information, concrete version, the shared library of concrete version comprise, the attribute information of concrete version shared library; Wherein comprise the positional information of shared library in version control server in the classification information of shared library; The Dependency Specification of described shared library comprises: the storehouse of the shared library that the storehouse of shared library indicates and relied on indicates;
The Access Management Access center is used for arriving first and searching corresponding descriptor in information database when needs obtain appointment JDK, obtains the file of this appointment JDK from version control server according to descriptor; Be used for when needs obtain the appointment shared library, arrive first and search corresponding shared library descriptor and shared library Dependency Specification in information database, obtain the file of this appointment shared library according to the shared library descriptor from version control server, obtain the file of other bag that is relied on by this appointment shared library according to the shared library Dependency Specification.
By as seen above-mentioned, the present invention is this to be saved in JDK and shared library on version control server, just the Dependency Specification of the descriptor of the descriptor of JDK and shared library and shared library is saved in information database, when needs obtain certain bag, at first obtain relevant information to information database, then obtain the technical scheme of concrete file from version control server, can reasonably manage JDK and shared library, in order to can be served fast, as one man quote by other.
Description of drawings
Fig. 1 is the service development framework schematic diagram in the embodiment of the present invention;
Fig. 2 is the schematic diagram of the concrete dependence in the embodiment of the present invention;
Fig. 3 is the process flow diagram of a kind of shared library management method in the embodiment of the present invention;
Fig. 4 is the composition structural representation of a kind of shared library management system in the embodiment of the present invention.
Embodiment
In order to make the purpose, technical solutions and advantages of the present invention clearer, describe the present invention below in conjunction with the drawings and specific embodiments.
Fig. 1 is the service development framework schematic diagram in the embodiment of the present invention.In Fig. 1, being described below of various piece:
The developer
Be used for developing and serve
Managerial personnel
Be used for checking, the various information of Monitoring Service.
The service development environment
Be used for the fast Development service
Create service, and produce service description information.
Produce the service code framework, the application service coding rule.
The existing service of inquiry
Compiling, packing, issuing service
Service for checking credentials consistance
Browser
Managerial personnel are used for by web server browsing service information.
Services package
Jar bag is used for issuing service
Version control server
Be used for preserving service code, service issue bag
Application server
Be used for operation service
The service information data storehouse
Preserve service description information
Preserve the service Dependency Specification
Preserve the service operation daily record
Web server
Realize inquiry, the monitoring of service.
Service will normally move, and must rely on other resources, and generally, its dependence can have following a few class:
JDK relies on
Shared library relies on
The third party wraps dependence
Share service relies on
Public service relies on
The instrument service relies on
Business service relies on
Brother's service relies on
That serves as seen that normal operation may rely on is surrounded by JDK and shared library, and wherein, shared library comprises: third party's bag and share service; Described share service comprises again: public service, instrument service, business service.
Except the dependence to bag, service also has the dependence to agreement, standard.But generally, can finally convert dependence to agreement, standard implementation bag to the dependence of agreement, standard, because the agreement of particular version, standard implementation bag be agreement, the standard of corresponding certain version necessarily, therefore just can the paired dependence of wrapping of secondary indication to the dependence of agreement, standard
Fig. 2 is the schematic diagram of the concrete dependence in the embodiment of the present invention.JDK does not rely on other any bags as seen from Figure 2.
If the JDK and the shared library that next management in the present invention are relied on describe so that other services can fast, as one man be quoted.
Fig. 3 is the process flow diagram of a kind of shared library management method in the embodiment of the present invention.As shown in Figure 3, comprising:
301, with the File Upload of the JDK assigned address to version control server, under the deposit position of the corresponding shared library classification with the File Upload of shared library in the version control server.
302, the descriptor of JDK is saved in information database.
Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server;
303, shared library descriptor and shared library Dependency Specification are saved in information database.
Wherein, the descriptor of described shared library comprises: the fileinfo that the shared library information of the classification information of shared library, shared library information, concrete version, the shared library of concrete version comprise, the attribute information of concrete version shared library; Wherein comprise the positional information of shared library in version control server in the classification information of shared library;
The Dependency Specification of described shared library comprises: the storehouse of the shared library that the storehouse of shared library indicates and relied on indicates;
304, when needs obtain appointment JDK, arrive first and search corresponding descriptor in information database, obtain the file of this appointment JDK from version control server according to descriptor.
305, when needs obtain the appointment shared library, arrive first and search corresponding shared library descriptor and shared library Dependency Specification in information database, obtain the file of this appointment shared library according to the shared library descriptor from version control server, obtain the file of other bag that is relied on by this appointment shared library according to the shared library Dependency Specification.
The below is to being the reasonable management of realizing JDK and shared library, and the data structure that adopts when preserving these information on information database describes:
1.JDK
For the JDK version that company need to support is set up a storehouse, all third party bag, the share service bag, and the service that belongs to a product all must show the JDK version of specifying its minimum that relies on.
The description of a JDK (jdk_version) information is as shown in table 1:
| Field name | Explanation of field | Data type | Major key | Could be sky | Default value and remarks |
| JdkVersionld | The Jdk version indicates | Int | PK | N | The self-propagation field |
| JdkVersion | The Jdk version | Varchar(10) | N | ||
| Repository | Deposit position | Nvarchar(256) | N |
Table 1
Remarks: set up unique index on JdkVersionId.
In table 1, deposit position refers to the deposit position of JDK on version control server.
2. shared library
Shared library is to share the bag that uses in global scope, comprising:
The third party wraps dependence
Share service relies on
Public service relies on
The instrument service relies on
Business service relies on
In case a bag enters shared platform, other developers just can promptly find and use this service, thereby effectively avoid the problem of overlapping development, unordered use
All shared library will be got up by an identical data structure managing of cover.In the present invention, the shared library category is distinguished.Classification (lib_id_mask, the shared_lib_category) information of shared library is as shown in table 2 and table 3.
Table 2
Remarks:
CategoryId produces the storehouse type designation with the mode of zonal coding
xxx xxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Level1 Level2 Level3 Level4 Level5 Level6 storehouse indicates the storehouse version
Generally speaking:
Level1: can define three major types: system-level, third party, our company
Later classification can be carried out classification separately according to different large classes, although show in the coding that provides above that the coded format of each classification is the same, in practice, can according to different situations, carry out different zonal codings to different classifications.
As seen in an embodiment of the present invention, classification indicates and is comprised of 64 bits, and wherein the 1-3 bit represents that first order classification, 4-8 bit represent that second level classification, 9-16 bit represent that third level classification, 17-24 bit represent that fourth stage classification, 25-32 bit represent that level V classification, 33-48 bit represent that the 6th grade of classification, 49-56 bit library representation indicate, the 57-64 bit indicates the storehouse version.
Table 3
Remarks:
Set up external bond on Parent, reference field is: lib_category.CategoryId
CategoryId produces the storehouse type designation with the mode of zonal coding
xxx xxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Level1 Level2 Level3 Level4 Level5 Level6 storehouse indicates the storehouse version
Generally speaking:
Level1: can define three major types: system-level, third party, our company
Later classification can be carried out classification separately according to different large classes, although show in the coding that provides above that the coded format of each classification is the same, in practice, can according to different situations, carry out different zonal codings to different classifications.
Repository: point to the deposit position of this shared library classification in version control server.
Shared library (share_lib) information is as shown in table 4:
Table 4
Remarks:
LibName: must use English alphabet, numeral, underscore, line character etc.
The deposit position of this shared library in version control server is the sub-directory under the deposit position of classification under this shared library, and subdirectory name is called " LibName ".
Shared library (share_versioned_lib) information of concrete version is as shown in table 5:
Table 5
Remarks:
LibName: must use English alphabet, numeral, underscore, line character etc.
The deposit position of this shared library in version control server is the sub-directory under the deposit position of classification under this shared library, and subdirectory name is called " LibName ".All versions of this shared vision all leave under a sub-directory of this position.The sub-directory title directly adopts version number.
File (share_versioned_lib_file) information that the shared library of concrete version comprises is as shown in table 6:
Table 6
Attribute (share_versioned_lib_property) information of concrete version shared library is as shown in table 7:
Table 7
Remarks:
Seq: when property value was too large, a property value may need multirow to come save data, and this is that standby Seq comes order of representation.Most of situation, property value can be used a line display, and in this case, Seq is always 1.
The dependence of shared library (share_versioned_lib_depedency) information is as shown in table 8:
Table 8
In an embodiment of the present invention, the concrete dependence of third party's bag can be divided into again two large classes: system-level and third party.
System-level some bags that belong to the java standard that show as are such as j2ee etc.
The classification that system-level bag is corresponding indicates and will adopt following rule:
xxx xxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Level1 Level2 Level3 Level4 Level5 Level6 storehouse indicates the storehouse version
■00001：http
■00010：ejb
■00011：xml
■00100：jms
■00101：jdbc
Level5: need not
Storehouse version: the storehouse of concrete version
The third party wraps corresponding classification sign will adopt following rule:
xxx xxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Level1 Level2 Level3 Level4 Level5 Level6 storehouse indicates the storehouse version
Level3: segmentation field
Storehouse version: the storehouse of concrete version
In an embodiment of the present invention,
Share service relies on exploitation and the service that be published to shared platform of dependence company that refers to.
Share service has three types
To instrument service, business service, provide the detailed description of method of servicing, to facilitate sharing of client.
The descriptor that is to say instrument service and business service also comprises: method information.
The method information of a concrete version shared library (instrument service or business service) is as shown in table 9:
Table 9
The data structure of the information of preserving in the information database of introducing previously.Based on operations such as above-mentioned data structure can increase newly shared library, discard, delete, shows and obtain.
Be specifically described as follows.
The solution of the present invention realizes the coherency management to enterprise's shared library, and this shared library comprises the share service of third-party shared library and company oneself exploitation; Concrete function comprises:
1. increase the shared library classification
Increase a record in the shared library classification; During increase, must specify following information: item name, classification are described, parent class
2. increase shared library
Increase a record in the shared library classification; During increase, must follow following steps:
1) find the classification of this shared library, if there is no, create it.
2) create this shared library,
A) library name
B) storehouse is described
C) storehouse type
D) storehouse provider
E) official website in storehouse
F) introduce reason
3) the particular version shared library of needs being uploaded, and following information is provided
A) bag version
B) the compliant Version this shop of this version
C) description of this version
D) the jdk version that needs
E) upload reason
F) service indicates (if this service is the share service of company oneself exploitation, needing to indicate)
G) license type
4) upload the shared library file to version control server, provide following information to each file simultaneously
A) file type
B) filename
5) if there are some specific properties in this storehouse, need specific properties is configured one by one; Particularly to the share service of enterprises exploitation, often need some attributes to simplify exploitation.
A) Property Name
B) attribute type
C) property value
6) if this storehouse has relied on other shared library, check each shared library, if the shared library version of this shared library and dependence exists, do not need to process this shared library; Otherwise
If a) shared library does not exist, must increase according to the logic that increases shared library shared library and the shared library version of this dependence;
B) if shared library exists, but the version that relies on do not exist, and must increase according to the logic that increases the shared library version shared library version of this dependence.
3. increase the shared library of concrete version
For shared library increases a shared library version, during increase, follow following steps:
1) find this shared library
2) the particular version shared library of needs being uploaded provides following information:
A) bag version
B) the compliant Version this shop of this version
C) description of this version
D) the jdk version that needs
E) upload reason
F) service indicates (if this service is the share service of company oneself exploitation, needing to indicate)
G) License type
3) upload the shared library file to version control server, provide following information to each file simultaneously:
A) file type
B) filename
4) if there are some specific properties in this storehouse, need specific properties is configured one by one; Particularly to the share service of enterprises exploitation, often need some attributes to simplify exploitation.
A) Property Name
B) attribute type
C) property value
5) if this storehouse has relied on other shared library, check each shared library, if the shared library version of this shared library and dependence exists, do not need to process this shared library; Otherwise
If a) shared library does not exist, must increase according to the logic that increases shared library shared library and the shared library version of this dependence;
B) if shared library exists, but the version that relies on do not exist, and must increase according to the logic that increases the shared library version shared library version of this dependence.
4. discard the shared library of particular version
The shared library that namely indicates a particular version is discarded state; After sign, later service can not be quoted this storehouse again.But quoting of having existed can continue to quote.
Discarded step is very simple:
1) find the particular version that needs discarded shared library.
2) click " confirmation ".
3) system will find out other shared library (third party's shared library, share service) of this shared library of dependence (directly with indirect); If shared library management and service-oriented shared exploitation are used together, find out simultaneously other services of developing that rely on this shared library.And they are shown.
4) after the user checks, can click " cancellation ", cancel this time operation; Also can select " confirmation ", continue discarded this version.
5. delete the shared library of particular version
Namely delete the shared library of a particular version; After deletion, this version will no longer exist.
The shared library that namely indicates a particular version is discarded state; After sign, later service can not be quoted this storehouse again.But quoting of having existed can continue to quote.
Discarded step is very simple:
1) find the particular version that needs discarded shared library.
2) click " confirmation ".
3) system will find out other shared library (third party's shared library, share service) of this shared library of dependence (directly with indirect); If shared library management and service-oriented shared exploitation are used together, find out simultaneously other services of developing that rely on this shared library.And they are shown.
4) if other shared library of Existence dependency and the service of developing are directly withdrawed from; Otherwise, show " cancellation " button, allow the user cancel this time operation; Show " confirmation " button, allow the user continue deletion.
6. show the shared library dependence of particular version
To the shared library of a particular version, show with graphics mode the dependence that they are all, be included in the upstream and downstream dependency chain the complete dependence of all services, shared library.
7. obtain a shared library
When a service need to be obtained third party's bag or share service from shared library, follow following steps:
1) find the specific category of this third party's bag or share service.
2) system shows all shared library under this classification, and relevant information.
3) if this system and service-oriented exploitation are used together, whether the system's brother service that will inquire about this service has relied on the shared library in identical shared library classification, if relied on, the shared library that relies on is chosen, as shared library and the shared library version of current dependence.Skip the 4th), 5) step, directly move the 6th) step;
4) if the shared library of not choosing in advance and version thereof are selected a shared library.Then, system lists all versions in the shared library of selection, and the user further selects the shared library version.
5) user clicks " confirmations ", and whether the dependence that system will verify the particular version of the shared library of selecting and service compatibility, as incompatible, points out error message, then returns to the 4th and goes on foot.
6) system will find the path of shared library in version control server, automatically download these files from version control server.If certainly cooperate with maven, can in the pom file, generate the dependence to the shared library of this version.
Next provide the composition structure of a kind of shared library management system in the present invention based on above-described embodiment.
Fig. 4 is the composition structural representation of a kind of shared library management system in the embodiment of the present invention.As shown in Figure 4, this system comprises: version control server 401, information database 402 and Access Management Access center 403, wherein:
Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server; The descriptor of described shared library comprises: the fileinfo that the shared library information of the classification information of shared library, shared library information, concrete version, the shared library of concrete version comprise, the attribute information of concrete version shared library; Wherein comprise the positional information of shared library in version control server in the classification information of shared library; The Dependency Specification of described shared library comprises: the storehouse of the shared library that the storehouse of shared library indicates and relied on indicates;
Access Management Access center 403 is used for arriving first and searching corresponding descriptor in information database 402 when needs obtain appointment JDK, obtains the file of this appointment JDK from version control server 401 according to descriptor; Be used for when needs obtain the appointment shared library, arrive first and search corresponding shared library descriptor and shared library Dependency Specification in information database 402, obtain the file of this appointment shared library according to the shared library descriptor from version control server 401, obtain the file of other bag that is relied on by this appointment shared library according to the shared library Dependency Specification.
Here, the Access Management Access center can be a functional component in service development environment in framework shown in Figure 1.
In system shown in Figure 4, described shared library comprises: third party's bag and share service; Wherein, described share service comprises: public service, instrument service, business service;
Wherein the descriptor of instrument service and service server also comprises: method information.
In system shown in Figure 4, preserve information by following data structure in described information database:
The sign of described JDK comprises: the JDK version indicates and the JDK version;
The data structure of the classification information of described shared library is: subregion sign, partition name, type mask, for the minimum value in this district, indicate for the maximum in this district, and classification sign, item name, classification description, classification mask, parent class, the positional information in version control server;
The data structure of described shared library information is: storehouse sign, classification sign, library name, storehouse description, storehouse type, storehouse provider, official website, introducing person, introduce reason, whether service out-of-date;
The data structure of the shared library information of described concrete version is: special description, JDK version sign, the uploader of storehouse signs of concrete version, storehouse signs, storehouse version, compliant Version this shop, this version, upload reason, serve sign, whether out-of-date, license type;
The data structure of the fileinfo that the shared library of concrete version comprises is: storehouse sign, file type, filename, the file path of concrete version;
The data structure of the attribute information of concrete version shared library is: storehouse sign, Property Name, COS sequence number, attribute type, the property value of concrete version.
In system shown in Figure 4, in described information database, described classification indicates and is comprised of 64 bits, and wherein the 1-3 bit represents that first order classification, 4-8 bit represent that second level classification, 9-16 bit represent that third level classification, 17-24 bit represent that fourth stage classification, 25-32 bit represent that level V classification, 33-48 bit represent that the 6th grade of classification, 49-56 bit library representation indicate, the 57-64 bit indicates the storehouse version.
In system shown in Figure 4, described Access Management Access center is further used for
Increase a record in the shared library classification;
And/or,
Increase a shared library in specifying classification: find the affiliated classification of this shared library, if there is no, create this classification; Create shared library, with the File Upload of shared library to version control server; If this shared library depends on other shared library, also need to increase described other shared library that relied on;
And/or,
The shared library of discarded indicated release;
And/or,
The shared library of deletion indicated release;
And/or,
The dependence of showing the shared library of indicated release.
In sum, the present invention is this to be saved in JDK and shared library on version control server, just the Dependency Specification of the descriptor of the descriptor of JDK and shared library and shared library is saved in information database, when needs obtain certain bag, at first obtain relevant information to information database, then obtain the technical scheme of concrete file from version control server, can reasonably manage JDK and shared library, in order to can be served fast, as one man quote by other.
The above is only preferred embodiment of the present invention, and is in order to limit the present invention, within the spirit and principles in the present invention not all, any modification of making, is equal to replacement, improvement etc., within all should being included in the scope of protection of the invention.
Claims (10)
1. a shared library management method, is characterized in that, the method comprises:
With the File Upload of the JDK assigned address to version control server, under the deposit position of the corresponding shared library classification with the File Upload of shared library in the version control server;
The descriptor of JDK is saved in information database; Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server;
Shared library descriptor and shared library Dependency Specification are saved in information database;
The descriptor of described shared library comprises: the fileinfo that the shared library information of the classification information of shared library, shared library information, concrete version, the shared library of concrete version comprise, the attribute information of concrete version shared library; Wherein comprise the positional information of shared library in version control server in the classification information of shared library;
The Dependency Specification of described shared library comprises: the storehouse of the shared library that the storehouse of concrete version shared library indicates and relied on indicates;
When needs obtain appointment JDK, arrive first and search corresponding descriptor in information database, obtain the file of this appointment JDK from version control server according to descriptor;
When needs obtain the appointment shared library, arrive first and search corresponding shared library descriptor and shared library Dependency Specification in information database, obtain the file of this appointment shared library according to the shared library descriptor from version control server, obtain the file of other bag that is relied on by this appointment shared library according to the shared library Dependency Specification;
Increase a shared library in specifying classification: find the affiliated classification of this shared library, if there is no, create this classification; Create shared library, with the File Upload of shared library to version control server; If this shared library depends on other shared library, also need to increase described other shared library that relied on.
2. method according to claim 1, is characterized in that,
Described shared library comprises: third party's bag and share service; Wherein, described share service comprises: public service, instrument service, business service;
Wherein the descriptor of instrument service and service server also comprises: method information.
3. method according to claim 1 and 2, is characterized in that,
The sign of described JDK comprises: the JDK version indicates and the JDK version;
The data structure of the classification information of described shared library is: subregion sign, partition name, type mask, for the minimum value in this district, indicate for the maximum in this district, and classification sign, item name, classification description, classification mask, parent class, the positional information in version control server;
The data structure of described shared library information is: storehouse sign, classification sign, library name, storehouse description, storehouse type, storehouse provider, official website, introducing person, introduce reason, whether service out-of-date;
The data structure of the shared library information of described concrete version is: special description, JDK version sign, the uploader of storehouse signs of concrete version, storehouse signs, storehouse version, compliant Version this shop, this version, upload reason, serve sign, whether out-of-date, license type;
The data structure of the fileinfo that the shared library of concrete version comprises is: storehouse sign, file type, filename, the file path of concrete version;
The data structure of the attribute information of concrete version shared library is: storehouse sign, Property Name, COS sequence number, attribute type, the property value of concrete version.
4. method according to claim 3, is characterized in that,
Described classification indicates and is comprised of 64 bits, and wherein the 1-3 bit represents that first order classification, 4-8 bit represent that second level classification, 9-16 bit represent that third level classification, 17-24 bit represent that fourth stage classification, 25-32 bit represent that level V classification, 33-48 bit represent that the 6th grade of classification, 49-56 bit library representation indicate, the 57-64 bit indicates the storehouse version.
5. method according to claim 3, is characterized in that, the method further comprises:
Increase a record in the shared library classification;
And/or,
The shared library of discarded indicated release;
And/or,
The shared library of deletion indicated release;
And/or,
The dependence of showing the shared library of indicated release.
6. a shared library management system, is characterized in that, this system comprises: version control server, information database and Access Management Access center, wherein:
Version control server is used for preserving JDK at the assigned address of self, and category is preserved shared library in the assigned address of self;
Information database, the descriptor that is used for preserving JDK, and the Dependency Specification of the descriptor of shared library and shared library;
Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server; The descriptor of described shared library comprises: the fileinfo that the shared library information of the classification information of shared library, shared library information, concrete version, the shared library of concrete version comprise, the attribute information of concrete version shared library; Wherein comprise the positional information of shared library in version control server in the classification information of shared library; The Dependency Specification of described shared library comprises: the storehouse of the shared library that the storehouse of shared library indicates and relied on indicates;
The Access Management Access center is used for arriving first and searching corresponding descriptor in information database when needs obtain appointment JDK, obtains the file of this appointment JDK from version control server according to descriptor; Be used for when needs obtain the appointment shared library, arrive first and search corresponding shared library descriptor and shared library Dependency Specification in information database, obtain the file of this appointment shared library according to the shared library descriptor from version control server, obtain the file of other bag that is relied on by this appointment shared library according to the shared library Dependency Specification; Be used for specifying classification to increase a shared library: find the affiliated classification of this shared library, if there is no, create this classification; Create shared library, with the File Upload of shared library to version control server; If this shared library depends on other shared library, also need to increase described other shared library that relied on.
7. system according to claim 6, is characterized in that,
Described shared library comprises: third party's bag and share service; Wherein, described share service comprises: public service, instrument service, business service;
Wherein the descriptor of instrument service and service server also comprises: method information.
8. according to claim 6 or 7 described systems, is characterized in that, preserves information by following data structure in described information database:
The sign of described JDK comprises: the JDK version indicates and the JDK version;
The data structure of the classification information of described shared library is: subregion sign, partition name, type mask, for the minimum value in this district, indicate for the maximum in this district, and classification sign, item name, classification description, classification mask, parent class, the positional information in version control server;
The data structure of described shared library information is: storehouse sign, classification sign, library name, storehouse description, storehouse type, storehouse provider, official website, introducing person, introduce reason, whether service out-of-date;
The data structure of the shared library information of described concrete version is: special description, JDK version sign, the uploader of storehouse signs of concrete version, storehouse signs, storehouse version, compliant Version this shop, this version, upload reason, serve sign, whether out-of-date, license type;
The data structure of the fileinfo that the shared library of concrete version comprises is: storehouse sign, file type, filename, the file path of concrete version;
The data structure of the attribute information of concrete version shared library is: storehouse sign, Property Name, COS sequence number, attribute type, the property value of concrete version.
9. system according to claim 8, is characterized in that, in described information database,
Described classification indicates and is comprised of 64 bits, and wherein the 1-3 bit represents that first order classification, 4-8 bit represent that second level classification, 9-16 bit represent that third level classification, 17-24 bit represent that fourth stage classification, 25-32 bit represent that level V classification, 33-48 bit represent that the 6th grade of classification, 49-56 bit library representation indicate, the 57-64 bit indicates the storehouse version.
10. system according to claim 8, is characterized in that, described Access Management Access center is further used for
Increase a record in the shared library classification;
And/or,
The shared library of discarded indicated release;
And/or,
The shared library of deletion indicated release;
And/or,
The dependence of showing the shared library of indicated release.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110182142 CN102393845B (en) | 2011-06-30 | 2011-06-30 | Shared library management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110182142 CN102393845B (en) | 2011-06-30 | 2011-06-30 | Shared library management method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102393845A CN102393845A (en) | 2012-03-28 |
| CN102393845B true CN102393845B (en) | 2013-06-05 |
Family
ID=45861170
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201110182142 Active CN102393845B (en) | 2011-06-30 | 2011-06-30 | Shared library management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102393845B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104572236B (en) * | 2015-01-07 | 2017-08-04 | 浪潮电子信息产业股份有限公司 | A fast construction method for Taurus project |
| CN108228229B (en) * | 2016-12-19 | 2021-04-13 | 深圳业拓讯通信科技有限公司 | Method and system for managing Maven dependence |
| CN107783757A (en) * | 2017-10-26 | 2018-03-09 | 福建中金在线信息科技有限公司 | A kind of code specification method and device |
| CN109101236A (en) * | 2018-07-06 | 2018-12-28 | 政采云有限公司 | The project that rule-based engine and maven plug-in unit are realized relies on management method and system |
| CN111158701B (en) * | 2019-12-18 | 2023-08-08 | 广州华多网络科技有限公司 | Library module issuing method, device, equipment and storage medium |
| CN111338651B (en) * | 2020-02-19 | 2023-04-21 | 北京字节跳动网络技术有限公司 | Method and device for providing download resource, and method and device for downloading resource |
| CN119025125A (en) * | 2023-05-26 | 2024-11-26 | 华为技术有限公司 | Method, device and electronic device for managing shared library |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1577268A (en) * | 2003-07-12 | 2005-02-09 | 三星电子株式会社 | Shared library system and method of building the system |
| CN1732458A (en) * | 2002-12-23 | 2006-02-08 | 摩托罗拉公司 | Method and apparatus for shared libraries on mobile devices |
-
2011
- 2011-06-30 CN CN 201110182142 patent/CN102393845B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1732458A (en) * | 2002-12-23 | 2006-02-08 | 摩托罗拉公司 | Method and apparatus for shared libraries on mobile devices |
| CN1577268A (en) * | 2003-07-12 | 2005-02-09 | 三星电子株式会社 | Shared library system and method of building the system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102393845A (en) | 2012-03-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102393845B (en) | Shared library management method and system | |
| US9256413B2 (en) | Automatic identification of services | |
| CN102325153B (en) | Service development method and system | |
| KR101176642B1 (en) | Programming interface for a computer flatform | |
| US8577904B2 (en) | Composite copy and paste for composite user interfaces | |
| US20130166550A1 (en) | Integration of Tags and Object Data | |
| US9218387B2 (en) | Cloud based master data management system and method therefor | |
| CN102253999B (en) | Verification method for service dependency | |
| CA2831381C (en) | Recovery of tenant data across tenant moves | |
| US20130013471A1 (en) | Location-based tax rate acquisition and management | |
| US20110029852A1 (en) | Metadata creation | |
| EP2973047A1 (en) | Methods for managing applications using semantic modeling and tagging and devices thereof | |
| EP3948545A1 (en) | Customizable enterprise automation test framework | |
| Rademacher et al. | Towards a UML profile for domain-driven design of microservice architectures | |
| US8060586B2 (en) | Dynamic web service deployment and integration | |
| US9053134B2 (en) | View variants in database schema mapping | |
| US11151100B2 (en) | Performing data quality functions using annotations | |
| WO2019109519A1 (en) | Service rule management method, apparatus and device, and computer-readable storage medium | |
| CN103019556A (en) | Quick help information display system and quick help information display method | |
| WO2013158513A1 (en) | Managing web extension through manifest file | |
| GB2504610A (en) | Managing data items using structured tags | |
| US20040142683A1 (en) | Programming interface layer of a service provider for data service delivery | |
| US8468159B2 (en) | Data element categorization in a service-oriented architecture | |
| CN109150940B (en) | Service object information sending method, service object information publishing method, server and client | |
| US20060136873A1 (en) | Application development performed independent of system landscape |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP02 | Change in the address of a patent holder | ||
| CP02 | Change in the address of a patent holder |
Address after: Room 810, 8 / F, 34 Haidian Street, Haidian District, Beijing 100080 Patentee after: BEIJING D-MEDIA COMMUNICATION TECHNOLOGY Co.,Ltd. Address before: 100089 Beijing city Haidian District wanquanzhuang Road No. 28 Wanliu new building A block 5 layer Patentee before: BEIJING D-MEDIA COMMUNICATION TECHNOLOGY Co.,Ltd. |