CN102393845A - Shared library management method and system - Google Patents
Shared library management method and system Download PDFInfo
- Publication number
- CN102393845A CN102393845A CN2011101821420A CN201110182142A CN102393845A CN 102393845 A CN102393845 A CN 102393845A CN 2011101821420 A CN2011101821420 A CN 2011101821420A CN 201110182142 A CN201110182142 A CN 201110182142A CN 102393845 A CN102393845 A CN 102393845A
- Authority
- CN
- China
- Prior art keywords
- version
- information
- classification
- jdk
- storehouse
- 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.)
- Granted
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 SB management method and system.
Background technology
The Internet era, the consumer improves the increasing 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 exploitation fast, quick deployment services; 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 introducing and upward has the problems such as introducing, incompatible introducing, inconsistent introducing that repeat; These problems are that the deployment of service from now on causes potential problem; Therefore how in full company, reasonably, correctly, consistance using and to manage third party library, is company's major issue that faces under development.In addition, for increasing Service Source; How to effectively utilize, multiplexing existing service, be to promoting the utilization factor of corporate resource, reducing cost plays a key effect.
Summary of the invention
The invention provides a kind of SB management method, this method can reasonably be managed JDK and SB, so that can served fast, as one man quote by other.
The present invention also provides a kind of SB management system, and this system can reasonably manage JDK and SB, so that can 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 SB management method, this method comprises:
The file of JDK is uploaded to the assigned address of version control server, the file of SB is uploaded under the deposit position of the corresponding SB classification in the version control server;
The descriptor of JDK is saved in the information database; Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server;
SB descriptor and SB dependence information are saved in the information database;
The descriptor of said SB comprises: the fileinfo that the SB information of the classification information of SB, SB information, concrete version, the SB of concrete version comprise, the attribute information of concrete version SB; Wherein comprise the positional information of SB in version control server in the classification information of SB;
The dependence information of said SB comprises: the storehouse of the SB that the storehouse of SB indicates and relied on indicates;
When needs obtain appointment JDK, arrive first and search corresponding descriptor in the information database, obtain the file of this appointment JDK from version control server according to descriptor;
When needs obtain the appointment SB; Arrive first and search corresponding SB descriptor and SB dependence information in the information database; Obtain the file of this appointment SB according to the SB descriptor from version control server, obtain the file of other bag that is relied on by this appointment SB according to SB dependence information.
The present invention also provides a kind of SB 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 SB in the assigned address of self;
Information database, the descriptor that is used to preserve JDK, and the dependence information of the descriptor of SB and SB;
Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server; The descriptor of said SB comprises: the fileinfo that the SB information of the classification information of SB, SB information, concrete version, the SB of concrete version comprise, the attribute information of concrete version SB; Wherein comprise the positional information of SB in version control server in the classification information of SB; The dependence information of said SB comprises: the storehouse of the SB that the storehouse of SB indicates and relied on indicates;
The Access Management Access center is used for when needs obtain appointment JDK, arriving first and searching corresponding descriptor in the information database, obtains the file of this appointment JDK from version control server according to descriptor; Be used for when needs obtain the appointment SB; Arrive first and search corresponding SB descriptor and SB dependence information in the information database; Obtain the file of this appointment SB according to the SB descriptor from version control server, obtain the file of other bag that is relied on by this appointment SB according to SB dependence information.
By above-mentioned visible; The present invention is this to be saved in JDK and SB on the version control server, and just the dependence information of the descriptor of the descriptor of JDK and SB and SB is saved in the information database, when needs obtain certain bag; At first to information database, obtain relevant information; Obtain the technical scheme of concrete file then from version control server, can reasonably manage JDK and SB, so that can served fast, as one man quote by other.
Description of drawings
Fig. 1 is the service development framework synoptic diagram in the embodiment of the invention;
Fig. 2 is the synoptic diagram of the concrete dependence in the embodiment of the invention;
Fig. 3 is the process flow diagram of a kind of SB management method in the embodiment of the invention;
Fig. 4 is the composition structural representation of a kind of SB management system in the embodiment of the invention.
Embodiment
In order to make the object of the invention, technical scheme and advantage clearer, describe the present invention below in conjunction with accompanying drawing and specific embodiment.
Fig. 1 is the service development framework synoptic diagram in the embodiment of the 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 developing fast serving
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 browsing information on services through the web server.
Services package
Jar bag is used for issuing service
Version control server
Be used for preserving service code, the service distribution bag
Application server
Be used for operation service
The service information data storehouse
Preserve service description information
Preserve service dependence information
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 speaking, its dependence can have following several types:
JDK relies on
SB 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
It is thus clear that serves that normal operation possibly rely on is surrounded by JDK and SB, wherein, SB comprises: third party's bag and share service; Said 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 speaking; Dependence to agreement, standard can finally convert the dependence that agreement, standard is realized bag to; Because the agreement of particular version, standard realize wrapping necessarily agreement, the standard of corresponding certain version, therefore just can the paired dependence of wrapping of secondary indication to the dependence of agreement, standard
Fig. 2 is the synoptic diagram of the concrete dependence in the embodiment of the invention.Can find out that by Fig. 2 JDK does not rely on other any bags.
If the JDK and the SB that next management among 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 SB management method in the embodiment of the invention.As shown in Figure 3, comprising:
301, the file of JDK is uploaded to the assigned address of version control server, the file of SB is uploaded under the deposit position of the corresponding SB classification in the version control server.
302, the descriptor of JDK is saved in the information database.
Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server;
303, SB descriptor and SB dependence information are saved in the information database.
Wherein, the descriptor of said SB comprises: the fileinfo that the SB information of the classification information of SB, SB information, concrete version, the SB of concrete version comprise, the attribute information of concrete version SB; Wherein comprise the positional information of SB in version control server in the classification information of SB;
The dependence information of said SB comprises: the storehouse of the SB that the storehouse of SB indicates and relied on indicates;
304, when needs obtain appointment JDK, arrive first and search corresponding descriptor in the information database, obtain the file of this appointment JDK from version control server according to descriptor.
305; When needs obtain the appointment SB; Arrive first and search corresponding SB descriptor and SB dependence information in the information database; Obtain the file of this appointment SB according to the SB descriptor from version control server, obtain the file of other bag that is relied on by this appointment SB according to SB dependence information.
In the face of the reasonable management for realization JDK and SB, the data structure that is adopted when on information database, preserving these information describes down:
1.JDK
For the JDK version that company need support is set up a storehouse, all third party's bags, share service bag, and all necessary JDK version of specifying the minimum that it relied on that shows of service that belongs to a product.
The description of a JDK (jdk_version) information is as shown in table 1:
The field title | 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: on JdkVersionId, set up unique index.
In the table 1, deposit position is meant the deposit position of JDK on version control server.
2. SB
SB is in global scope, to share the bag that uses, and 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 gets into shared platform, other developers just can promptly find and use this service, thereby avoid the problem of overlapping development, unordered use effectively
All SBs will get up through the identical data structure managing of a cover.In the present invention, the SB category is distinguished.(lib_id_mask, shared_lib_category) information is shown in table 2 and table 3 for the classification of SB.
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 big classes, though above show that the coded format of each classification is the same in the coding that provides, in the practice, can carry out the different partition areas coding to different classes according to condition of different.
It is thus clear that in an embodiment of the present invention; Classification indicates to be made up of 64 bits, and wherein the 1-3 bit representes 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, 57-64 bit sign storehouse version.
Table 3
Remarks:
On Parent, set up external bond, 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 big classes, though above show that the coded format of each classification is the same in the coding that provides, in the practice, can carry out the different partition areas coding to different classes according to condition of different.
Repository: point to the deposit position of this SB classification in version control server.
SB (share_lib) information is as shown in table 4:
Table 4
Remarks:
LibName: must be with English alphabet, numeral, underscore, line character etc.
The deposit position of this SB in version control server is the sub-directory under the deposit position of classification under this SB, and subdirectory name is called " LibName ".
SB (share_versioned_lib) information of concrete version is as shown in table 5:
Table 5
Remarks:
LibName: must be with English alphabet, numeral, underscore, line character etc.
The deposit position of this SB in version control server is the sub-directory under the deposit position of classification under this SB, and subdirectory name is called " LibName ".All versions of this shared vision all leave under the sub-directories of this position.The sub-directory title directly adopts version number.
File (share_versioned_lib_file) information that the SB of concrete version comprises is as shown in table 6:
Table 6
Attribute (share_versioned_lib_property) information of concrete version SB is as shown in table 7:
Table 7
Remarks:
Seq: when property value was too big, a property value possibly need multirow to preserve 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 SB (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 two big types again: system-level and third party.
System-level some bags that belong to the java standard that show as are such as j2ee etc.
Rule below system-level bag corresponding class indicates and will adopt:
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
Level6: need not
The third party wraps the corresponding class 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
Level1:010 representes that the third party wraps
Level2: the expression third party wraps corresponding field, such as
00001:http
00010:xml
Level3: segmentation field
Level5: more smart her cloth segments the field
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 is meant.
Share service has three types
instrument service: support the hot plug function, have service interface and a plurality of method of servicing.
business service: support the hot plug function, have service interface and a plurality of method of servicing.
To instrument service, business service, the detailed description of method of servicing is provided, to make things convenient for 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 SB (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 that the front is introduced.Based on operations such as above-mentioned data structure can increase newly, discard, delete, show and obtain SB.
The concrete introduction as follows.
Scheme of the present invention realizes the coherency management to enterprise's SB, and this SB comprises the share service of third-party SB and company oneself exploitation; Concrete function comprises:
The SB of
deletion particular version
1. increase the SB classification
In the SB classification, increase a record; During increase, must specify following information: item name, classification are described, parent class
2. increase SB
In the SB classification, increase a record; During increase, must follow following steps:
1) finds the classification of this SB,, then create it if do not exist.
2) create this SB,
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 SB 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, then needing to indicate)
G) license type
4) upload the SB file to version control server, to each file following information is provided simultaneously
A) file type
B) filename
5) if there are some specific properties in this storehouse, then need specific properties be disposed one by one; Particularly, often need some attributes to simplify exploitation to the share service of enterprises exploitation.
A) Property Name
B) attribute type
C) property value
6) if this storehouse has relied on other SBs, then check each SB,, then need not handle this SB if the SB version of this SB and dependence exists; Otherwise
If a) SB does not exist, then must increase the SB and the SB version of this dependence according to the logic that increases SB;
B) if SB exists, but the version that relies on do not exist, and then must increase the SB version of this dependence according to the logic that increases the SB version.
3. increase the SB of concrete version
For SB increases a SB version, during increase, follow following steps:
1) finds this SB
2) the particular version SB 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, then needing to indicate)
G) License type
3) upload the SB file to version control server, to each file following information be provided simultaneously:
A) file type
B) filename
4) if there are some specific properties in this storehouse, then need specific properties be disposed one by one; Particularly, often need some attributes to simplify exploitation to the share service of enterprises exploitation.
A) Property Name
B) attribute type
C) property value
5) if this storehouse has relied on other SBs, then check each SB,, then need not handle this SB if the SB version of this SB and dependence exists; Otherwise
If a) SB does not exist, then must increase the SB and the SB version of this dependence according to the logic that increases SB;
B) if SB exists, but the version that relies on do not exist, and then must increase the SB version of this dependence according to the logic that increases the SB version.
4. discard the SB of particular version
The SB that promptly indicates a particular version is discarded state; After the sign, later service can not be quoted this storehouse again.But quoting of having existed then can continue to quote.
Discarded step is very simple:
1) finds the particular version that needs discarded SB.
2) click " affirmation ".
3) system will find out other SBs (third party's SB, share service) of this SB of dependence (directly with indirect); If SB management and service-oriented shared exploitation are used together, then find out other services of developing that rely on this SB simultaneously.And they are shown.
4) after the customer inspection, can click " cancellation ", cancel this time operation; Also can select " affirmation ", continue discarded this version.
5. delete the SB of particular version
Promptly delete the SB of a particular version; After the deletion, this version will no longer exist.
The SB that promptly indicates a particular version is discarded state; After the sign, later service can not be quoted this storehouse again.But quoting of having existed then can continue to quote.
Discarded step is very simple:
1) finds the particular version that needs discarded SB.
2) click " affirmation ".
3) system will find out other SBs (third party's SB, share service) of this SB of dependence (directly with indirect); If SB management and service-oriented shared exploitation are used together, then find out other services of developing that rely on this SB simultaneously.And they are shown.
4) if having other SB that relies on and the service of developing, then directly withdraw from; Otherwise, show " cancellation " button, let the user cancel this time operation; Show " affirmation " button, let the user continue deletion.
6. the SB dependence of showing particular version
To the SB of a particular version, show its all dependence with graphics mode, be included in the upstream and downstream dependency chain the complete dependence of all services, SB.
7. obtain a SB
When a service need be obtained third party's bag or share service from SB, follow following steps:
1) finds the perhaps specific category of share service of this third party's bag.
2) system shows all SBs under this classification, and relevant information.
3) if this system and service-oriented exploitation are used together; Then whether the system's brother service that will inquire about this service has relied on the SB in the identical SB classification; If relied on, then the SB that relies on is chosen, as the SB and the SB version of current dependence.Skip the 4th), 5) step, directly move the 6th) step;
4) if SB of not choosing in advance and version thereof are then selected a SB.Then, system lists all versions in the SB of selection, and the user further selects the SB version.
5) user clicks " affirmations ", and system will verify the dependence compatibility whether of particular version and the service of the SB of selecting, and as incompatible, then point out error message, return the 4th then and go on foot.
6) system will find the path of SB in version control server, from version control server, download these files automatically.If cooperate with maven certainly, then can in the pom file, generate dependence to the SB of this version.
Next provide the composition structure of a kind of SB management system among the present invention based on the foregoing description.
Fig. 4 is the composition structural representation of a kind of SB management system in the embodiment of the invention.As shown in Figure 4, this system comprises: version control server 401, information database 402 and Access Management Access center 403, wherein:
Version control server 401 is used for preserving JDK at the assigned address of self, and category is preserved SB in the assigned address of self;
Information database 402, the descriptor that is used to preserve JDK, and the dependence information of the descriptor of SB and SB;
Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server; The descriptor of said SB comprises: the fileinfo that the SB information of the classification information of SB, SB information, concrete version, the SB of concrete version comprise, the attribute information of concrete version SB; Wherein comprise the positional information of SB in version control server in the classification information of SB; The dependence information of said SB comprises: the storehouse of the SB that the storehouse of SB indicates and relied on indicates;
Access Management Access center 403 is used for when needs obtain appointment JDK, arriving first and searching corresponding descriptor in the information database 402, obtains the file of this appointment JDK from version control server 401 according to descriptor; Be used for when needs obtain the appointment SB; Arrive first and search corresponding SB descriptor and SB dependence information in the information database 402; Obtain the file of this appointment SB according to the SB descriptor from version control server 401, obtain the file of other bag that is relied on by this appointment SB according to SB dependence information.
Here, the Access Management Access center can be a functional component in the service development environment in the framework shown in Figure 1.
In system shown in Figure 4, said SB comprises: third party's bag and share service; Wherein, said 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 the said information database:
The sign of said JDK comprises: the JDK version indicates and the JDK version;
The data structure of the classification information of said SB is: subregion sign, partition name, type mask, to the minimum value in this district, indicate to 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 said SB 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 SB information of said 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 SB 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 SB is: storehouse sign, Property Name, COS sequence number, attribute type, the property value of concrete version.
In system shown in Figure 4; In said information database; Said classification indicates to be made up of 64 bits, and wherein the 1-3 bit representes 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, 57-64 bit sign storehouse version.
In system shown in Figure 4, said Access Management Access center is further used for
In the SB classification, increase a record;
And/or,
In specifying classification, increase a SB: find the affiliated classification of this SB,, then create this classification if do not exist; Create SB, the file of SB is uploaded to version control server; If this SB depends on other SB, then also need increase said other SBs that relied on;
And/or,
The SB of discarded indicated release;
And/or,
The SB of deletion indicated release;
And/or,
The dependence of showing the SB of indicated release.
In sum; The present invention is this to be saved in JDK and SB on the version control server, and just the dependence information of the descriptor of the descriptor of JDK and SB and SB is saved in the information database, when needs obtain certain bag; At first to information database, obtain relevant information; Obtain the technical scheme of concrete file then from version control server, can reasonably manage JDK and SB, so that can served fast, as one man quote by other.
The above is merely preferred embodiment of the present invention, and is in order to restriction the present invention, not all within spirit of the present invention and principle, any modification of being made, is equal to replacement, improvement etc., all should be included within the scope that the present invention protects.
Claims (10)
1. a SB management method is characterized in that, this method comprises:
The file of JDK is uploaded to the assigned address of version control server, the file of SB is uploaded under the deposit position of the corresponding SB classification in the version control server;
The descriptor of JDK is saved in the information database; Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server;
SB descriptor and SB dependence information are saved in the information database;
The descriptor of said SB comprises: the fileinfo that the SB information of the classification information of SB, SB information, concrete version, the SB of concrete version comprise, the attribute information of concrete version SB; Wherein comprise the positional information of SB in version control server in the classification information of SB;
The dependence information of said SB comprises: the storehouse of the SB that the storehouse of concrete version SB indicates and relied on indicates;
When needs obtain appointment JDK, arrive first and search corresponding descriptor in the information database, obtain the file of this appointment JDK from version control server according to descriptor;
When needs obtain the appointment SB; Arrive first and search corresponding SB descriptor and SB dependence information in the information database; Obtain the file of this appointment SB according to the SB descriptor from version control server, obtain the file of other bag that is relied on by this appointment SB according to SB dependence information.
2. method according to claim 1 is characterized in that,
Said SB comprises: third party's bag and share service; Wherein, said 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 said JDK comprises: the JDK version indicates and the JDK version;
The data structure of the classification information of said SB is: subregion sign, partition name, type mask, to the minimum value in this district, indicate to 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 said SB 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 SB information of said 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 SB 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 SB 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,
Said classification indicates to be made up of 64 bits, and wherein the 1-3 bit representes 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, 57-64 bit sign storehouse version.
5. method according to claim 3 is characterized in that, this method further comprises:
In the SB classification, increase a record;
And/or,
In specifying classification, increase a SB: find the affiliated classification of this SB,, then create this classification if do not exist; Create SB, the file of SB is uploaded to version control server; If this SB depends on other SB, then also need increase said other SBs that relied on;
And/or,
The SB of discarded indicated release;
And/or,
The SB of deletion indicated release;
And/or,
The dependence of showing the SB of indicated release.
6. a SB 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 SB in the assigned address of self;
Information database, the descriptor that is used to preserve JDK, and the dependence information of the descriptor of SB and SB;
Wherein, the descriptor of JDK comprises: the sign of JDK and the JDK deposit position on version control server; The descriptor of said SB comprises: the fileinfo that the SB information of the classification information of SB, SB information, concrete version, the SB of concrete version comprise, the attribute information of concrete version SB; Wherein comprise the positional information of SB in version control server in the classification information of SB; The dependence information of said SB comprises: the storehouse of the SB that the storehouse of SB indicates and relied on indicates;
The Access Management Access center is used for when needs obtain appointment JDK, arriving first and searching corresponding descriptor in the information database, obtains the file of this appointment JDK from version control server according to descriptor; Be used for when needs obtain the appointment SB; Arrive first and search corresponding SB descriptor and SB dependence information in the information database; Obtain the file of this appointment SB according to the SB descriptor from version control server, obtain the file of other bag that is relied on by this appointment SB according to SB dependence information.
7. system according to claim 6 is characterized in that,
Said SB comprises: third party's bag and share service; Wherein, said 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, it is characterized in that, preserve information by following data structure in the said information database:
The sign of said JDK comprises: the JDK version indicates and the JDK version;
The data structure of the classification information of said SB is: subregion sign, partition name, type mask, to the minimum value in this district, indicate to 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 said SB 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 SB information of said 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 SB 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 SB 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 said information database,
Said classification indicates to be made up of 64 bits, and wherein the 1-3 bit representes 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, 57-64 bit sign storehouse version.
10. system according to claim 8 is characterized in that, said Access Management Access center is further used for
In the SB classification, increase a record;
And/or,
In specifying classification, increase a SB: find the affiliated classification of this SB,, then create this classification if do not exist; Create SB, the file of SB is uploaded to version control server; If this SB depends on other SB, then also need increase said other SBs that relied on;
And/or,
The SB of discarded indicated release;
And/or,
The SB of deletion indicated release;
And/or,
The dependence of showing the SB 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 true CN102393845A (en) | 2012-03-28 |
CN102393845B 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) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104572236A (en) * | 2015-01-07 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | Fast building method for Taurus project |
CN107783757A (en) * | 2017-10-26 | 2018-03-09 | 福建中金在线信息科技有限公司 | A kind of code specification method and device |
CN108228229A (en) * | 2016-12-19 | 2018-06-29 | 深圳业拓讯通信科技有限公司 | The management method and system that a kind of Maven is relied on |
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 |
CN111158701A (en) * | 2019-12-18 | 2020-05-15 | 广州华多网络科技有限公司 | Library module publishing method, device, equipment and storage medium |
CN111338651A (en) * | 2020-02-19 | 2020-06-26 | 北京字节跳动网络技术有限公司 | Method and device for providing downloaded resources and method and device for downloading resources |
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 |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104572236A (en) * | 2015-01-07 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | Fast building method for Taurus project |
CN104572236B (en) * | 2015-01-07 | 2017-08-04 | 浪潮电子信息产业股份有限公司 | A kind of Taurus projects fast construction building method |
CN108228229A (en) * | 2016-12-19 | 2018-06-29 | 深圳业拓讯通信科技有限公司 | The management method and system that a kind of Maven is relied on |
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 |
CN111158701A (en) * | 2019-12-18 | 2020-05-15 | 广州华多网络科技有限公司 | Library module publishing method, device, equipment and storage medium |
CN111158701B (en) * | 2019-12-18 | 2023-08-08 | 广州华多网络科技有限公司 | Library module issuing method, device, equipment and storage medium |
CN111338651A (en) * | 2020-02-19 | 2020-06-26 | 北京字节跳动网络技术有限公司 | Method and device for providing downloaded resources and method and device for downloading resources |
CN111338651B (en) * | 2020-02-19 | 2023-04-21 | 北京字节跳动网络技术有限公司 | Method and device for providing download resource, and method and device for downloading resource |
Also Published As
Publication number | Publication date |
---|---|
CN102393845B (en) | 2013-06-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN102325153B (en) | Service development method and system | |
CN102393845B (en) | Shared library management method and system | |
US20190155821A1 (en) | Related table notifications | |
US11366805B2 (en) | Integrated entity view across distributed systems | |
US20130166550A1 (en) | Integration of Tags and Object Data | |
AU2019236628B2 (en) | Integrated entity view across distributed systems | |
US9218387B2 (en) | Cloud based master data management system and method therefor | |
CN102253999B (en) | Verification method for service dependency | |
US20130013471A1 (en) | Location-based tax rate acquisition and management | |
US20130268561A1 (en) | Systems and methods for compressing and extracting information from marketplace taxonomies | |
Rademacher et al. | Towards a UML profile for domain-driven design of microservice architectures | |
US20130290244A1 (en) | Cloud Based Master Data Management System and Method Therefor | |
US20150186808A1 (en) | Contextual data analysis using domain information | |
US20180321820A1 (en) | Application extension | |
US11151100B2 (en) | Performing data quality functions using annotations | |
CN103019556A (en) | Quick help information display system and quick help information display method | |
US20130091099A1 (en) | Migrating artifacts between service-oriented architecture repositories | |
US11604765B2 (en) | Database and file structure configurations for managing text strings to be provided by a graphical user interface | |
Kefalakis et al. | A visual paradigm for IoT solutions development | |
GB2504610A (en) | Managing data items using structured tags | |
US20170193409A1 (en) | Business resource modeling | |
US20190295097A1 (en) | Cross-functional analytics tool for integrating web analytics data and customer relationship management data | |
Fensel et al. | Bringing online visibility to hotels with schema. org and multi-channel communication | |
US11036763B2 (en) | Flexible organizational hierarchy | |
CN109150940B (en) | Service object information sending method, service object information publishing method, server and client |
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. |