CN103383646B - A kind of Groovy script loading method and device - Google Patents

Abstract

The application discloses a Groovy script loading method and device, which are used to solve the problem of low scalability and use flexibility of the Groovy script in the prior art. This method reads the Groovy script, obtains the attribute information of the Groovy script, generates the corresponding XML configuration file and loads it into the Spring context, and finally loads the Groovy script into the Spring context as a JavaBean. Since multiple JavaBeans under the Spring framework can refer to each other, the Groovy script is loaded into the Spring context as a JavaBean. The Groovy script can directly refer to other JavaBean, and other JavaBean can also directly refer to the Groovy script, thereby improving the reliability of the Groovy script. Scalability and flexibility of use.

Description

A Groovy script loading method and device

technical field

The present application relates to the technical field of communications, and in particular to a Groovy script loading method and device.

Background technique

Groovy is an emerging Java2 platform language. Because it can be well combined with Java code, Groovy can be used for Java programming on the Java platform, so Groovy is widely used in various fields.

For example, when the local system needs to interact with at least one external system, since the formats of the packets used by each external system are different, and the local system does not support the format of the packets sent by the external system, it is necessary to Establish an interactive platform with the external system, and the interactive platform will uniformly convert the format of the message used by the external system into a format supported by the local system, and then send it to the local system for analysis. Specifically, a format conversion function module is set in the interactive platform, and the format conversion function module can use the written Groovy script to convert the message format.

In the prior art, the process of using Groovy scripts for message format conversion is specifically, the format conversion function module compiles the written Groovy scripts through the Groovy ClassLoader (GroovyClassLoader), and after the compilation is successful, loads the Groovy scripts through the GroovyClassLoader Script, complete the corresponding function through the loaded Groovy script.

However, when using the above method to load the Groovy script, if the function of the Groovy script needs to be expanded subsequently, such as adding the functions of other functional modules existing in the interactive platform, the entire Groovy script needs to be rewritten and loaded into the format again. Convert function modules. And if the script in some other functional module of the interactive platform also needs to increase the function of the Groovy script, the script in the other functional module also needs to be rewritten and loaded. Therefore, the Groovy script loading method in the prior art reduces the scalability of the Groovy script, and also reduces the flexibility of using the Groovy script.

Contents of the invention

The embodiments of the present application provide a Groovy script loading method and device, which are used to solve the problem of low scalability and use flexibility of the Groovy script in the prior art.

A Groovy script loading method provided in the embodiment of the present application includes:

The Spring script loader reads Groovy scripts stored in the database; and

Obtain the attribute information of the Groovy script, generate a corresponding Extensible Markup Language XML configuration file according to the acquired attribute information, and load it into the Spring context; and

Load the Groovy script as a JavaBean into the Spring context, and provide other JavaBean loaded in the Spring context to the loaded Groovy script reference, or provide the loaded Groovy script to other JavaBean references loaded in the Spring context .

A Groovy script loading device provided in an embodiment of the present application includes:

Groovy script cache management unit, used to read Groovy scripts stored in the database;

The Spring Extensible Markup Language XML configuration assembly unit is used to obtain the attribute information of the Groovy script, generate a corresponding XML configuration file according to the obtained attribute information, and load it into the Spring context;

The Bean processor Processor unit is used to load the Groovy script into the Spring context as a JavaBean, and provide other JavaBean loaded in the Spring context to the loaded Groovy script reference, or provide the loaded Groovy script to Other JavaBean references loaded in the Spring context.

The embodiment of the present application provides a Groovy script loading method and device, in which the Spring script loader reads the Groovy script stored in the database, obtains the attribute information of the Groovy script, generates a corresponding XML configuration file and loads it into the Spring context, Finally, the Groovy script is loaded into the Spring context as a JavaBean. Since multiple JavaBeans under the Spring framework can refer to each other as needed, the Groovy script is loaded into the Spring context as a JavaBean in the embodiment of this application, so that the Groovy script can directly refer to the Other JavaBean, when other JavaBean needs to extend the function of the Groovy script, can also directly refer to the Groovy script which is also a JavaBean, thereby improving the scalability and flexibility of the Groovy script.

Description of drawings

Fig. 1 is the Groovy script loading process that the embodiment of the present application provides;

Fig. 2 is the detailed process that the Groovy script loading that the embodiment of the present application provides;

Fig. 3 is the Groovy script loading device that the embodiment of the present application provides;

FIG. 4 is a schematic diagram of a specific implementation structure of a Spring script loader provided in an embodiment of the present application.

detailed description

Since the Groovy syntax is similar to the Java syntax, in the embodiment of this application, the Groovy script written as a JavaBean is loaded into the Spring context (SpringContext) through the Spring script loader, and since multiple JavaBean in the Spring context can refer to each other, Therefore, the Groovy script can directly refer to other JavaBeans in the Spring context, and other JavaBeans can also refer to the Groovy script that is also a JavaBean, thereby improving the scalability and flexibility of the Groovy script.

The embodiments of the present application will be described in detail below in conjunction with the accompanying drawings.

Fig. 1 is the Groovy script loading process that the embodiment of the present application provides, specifically comprises the following steps:

S101: The Spring script loader reads the Groovy script stored in the database.

In the embodiment of the present application, the written Groovy script can be stored in the database, of course, it can also be stored in other storages. The Groovy script cache management unit in the Spring script loader reads the Groovy script. Specifically, it can read the Groovy script stored in the database when the system where the Spring script loader is located starts, or periodically read the Groovy script. It can also be used as Read the Groovy script when the Groovy script in the database changes, for example, a new Groovy script is added to the database, or a Groovy script is updated.

S102: Obtain attribute information of the Groovy script, generate a corresponding Extensible Markup Language (Extensible Markup Language, XML) configuration file according to the acquired attribute information, and load it into the Spring context.

Since when a JavaBean is loaded into the Spring context, the attribute information of the JavaBean must first be loaded, including attribute information such as the Bean ID or class name (ClassName) of the JavaBean, so the SpringXML configuration assembly in the Spring script loader in the embodiment of this application The unit acquires property information of the Groovy script. Since the attribute information of the JavaBean needs to be loaded through the XML configuration file when it is loaded into the Spring context, the SpringXML configuration assembly unit generates the corresponding XML configuration file according to the acquired attribute information of the Groovy script, and loads it into the Spring context.

For example, according to the obtained ClassName of the Groovy script, the corresponding XML configuration file is generated as follows:

After generating the above XML configuration file, the SpringXML configuration assembly unit can load the above XML configuration file into the Spring context, wherein the SpringXML configuration assembly unit in the embodiment of this application can be Spring's XmlBeanDefinitionReader.

S103: Load the Groovy script into the Spring context as a JavaBean.

In the embodiment of this application, after the attribute information of the Groovy script is loaded into the Spring context, the Bean processor (Processor) unit in the Spring script loader can load the Groovy script as a JavaBean into the Spring context, When the function of the Groovy script needs to be extended, other JavaBean loaded in the Spring context will be provided to the loaded Groovy script reference, and when other JavaBean in the Spring context needs to extend the function of the Groovy script, the Groovy script will be loaded The script provides references to other JavaBeans loaded in the Spring context.

The Spring context can be regarded as a Spring container, and multiple JavaBeans are loaded in the container, and each JavaBean can complete the corresponding function, and for one of the JavaBean, the JavaBean can refer to one or several other JavaBean loaded in the container. A JavaBean can also be referenced by one or several other JavaBean loaded in the container. Therefore, in the embodiment of this application, the Groovy script is loaded into the Spring context as a JavaBean, which can be conveniently referred to by other loaded JavaBean. Extending the function of the Groovy script can also enable other JavaBeans to flexibly refer to the Groovy script, thereby improving the scalability and flexibility of the Groovy script.

For example, the function of the Groovy script is to convert the format of the message sent by the external system into a format supported by the local system. If the function of the Groovy script is to be extended to first decrypt the message sent by the external system, and then decrypt the format conversion of the message, then in the embodiment of the present application, after the Groovy script is loaded into the Spring context as a JavaBean, it can directly refer to another JavaBean with decryption function loaded in the Spring context, without rewriting the entire Groovy script , thus improving the scalability of Groovy scripts. Correspondingly, if other JavaBeans loaded in the Spring context want to extend the message format conversion function, they can also directly reference the Groovy script that is also a JavaBean, thereby improving the flexibility of using the Groovy script.

In the embodiment of the present application, in order to improve the loading speed of the Groovy script as much as possible, in the above step S101, when the Spring script loader reads the Groovy script stored in the database, the Groovy script stored in the database is read into the cache , so that when the subsequent steps S102 and S103 are executed, generating and loading the property information of the Groovy script and loading the Groovy script are also performed in the cache, that is, the entire Spring context exists in the cache. This can not only improve the loading speed of the Groovy script, but also save the need to restart the entire system where the Spring script loader is located when loading a new script, and only need to refresh the cache.

In the embodiment of the present application, in order to improve the accuracy of the Groovy script loaded by subsequent use, before the Spring script loader loads the Groovy script as a JavaBean into the Spring context, that is, before step S103 shown in FIG. 1 , Also check the grammar of the Groovy script, and determine that the grammar check of the Groovy script passes. Among them, the syntax checking unit in the Spring script loader can check the syntax of the Groovy script, that is, compile the Groovy script, and then load the Groovy script into the Spring context as a JavaBean after the compilation is passed, otherwise it prompts to compile mistake.

Moreover, considering that in practical applications, ordinary syntax checking only checks whether the syntax of the Groovy script is correct, such as the GroovyClassLoader that comes with Groovy. If only one name is defined in the Groovy script, such as test, its grammar is not wrong, so the normal grammar check will consider that the grammar check of the Groovy script with only one name defined is passed. But in fact, the Groovy script does not have any other functions except the defined name, that is, it does not function as a JavaBean, so it does not make any sense to load the Groovy script as a JavaBean into the Spring context.

In the embodiment of the present application, in order to avoid the problem that the above-mentioned Groovy script is not standardized, so that there is no doubt about loading the Groovy script, the method for checking the syntax of the Groovy script is specifically to determine whether the Groovy script contains at least one element inherited from the set base For the subclass of the class, when the judgment result is yes, it is determined that the grammar check of the Groovy script is passed; otherwise, it is determined that the grammar check of the Groovy script is not passed.

That is to say, in the embodiment of the present application, in addition to performing ordinary syntax checking on the Groovy script, it is also necessary to check whether the Groovy script contains at least one subclass inherited from the set base class, wherein the set base class can be Set as required. For example, when the Groovy script is used to convert the format of the message sent by the external system, the setting base class can be set as the base class with the format conversion function, but the base class does not include which external system The format conversion is performed on the sent message, or which port of the external system sent the message, or the message in which format. The Groovy script includes a subclass inherited from the above-mentioned base class, which means that the format conversion function of the base class is specifically applied to the message sent by the external system, or the message sent by the port of the external system , or the subclass of the format of the message for which the format conversion is performed.

Continuing with the above example, assume that the Groovy script is used to convert the formats of messages sent by external system A and external system B, where external system A sends messages in format a, and external system B sends messages in format b. If the local system can only parse messages of format c, two base classes can be set, the first is a method for converting format a to format c, and the second is a method for converting format b to format c. A subclass in the Groovy script inherits from the first base class, that is, the message sent by the external system A in format a is converted into a message in format c by the method of the first base class, and another subclass Inherited from the second base class, that is to convert the message sent by the external system B in format b into a message in format c through the method of the second base class. Therefore, when using the method of the embodiment of the present application to check the grammar of the Groovy script, it is determined that the Groovy script contains at least one subclass inherited from the set base class, and the grammar check passes. And if only one name is defined in the Groovy script, such as being defined as test, then when using the method of the embodiment of the present application to check the grammar, although the common grammar is not wrong, the Groovy script does not include any character inherited from the set base. class, so the syntax check fails.

Through the above grammar check provided by the embodiment of the present application, when the grammar check fails, a compilation error is prompted, and when the grammar check passes, the Spring script loader loads the Groovy script as a JavaBean into the Spring context. In order to improve the response speed of the system where the Spring script loader is located, the Groovy script is loaded in a lazy loading manner in the embodiment of the present application, that is, the Groovy script is loaded into the Spring context as a JavaBean in a lazy loading manner.

Fig. 2 is the detailed process of loading the Groovy script provided by the embodiment of the present application, which specifically includes the following steps:

S201: The Spring script loader reads the Groovy script stored in the database into the cache.

S202: Obtain attribute information of the Groovy script, generate a corresponding XML configuration file according to the acquired attribute information, and load it into the Spring context.

S203: Determine whether the grammar in the Groovy script is correct, if the determination result is yes, execute step S204, otherwise execute step S206.

S204: Judging whether the Groovy script contains at least one subclass inherited from the set base class, if the judging result is yes, go to step S205, otherwise go to step S206.

S205: Load the Groovy script as a JavaBean into the Spring context in a lazy loading manner.

S206: A compilation error is prompted.

Wherein, the execution order of step S203 and step S204 in the above process is not in particular order.

Fig. 3 is the Groovy script loading device that the embodiment of the present application provides, specifically includes:

Groovy script cache management unit 301, used to read the Groovy script stored in the database;

The SpringXML configuration assembly unit 302 is used to obtain the attribute information of the Groovy script, generate a corresponding XML configuration file according to the obtained attribute information, and load it into the Spring context;

The BeanProcessor unit 303 is used to load the Groovy script as a JavaBean into the Spring context, and provide other JavaBean loaded in the Spring context to the loaded Groovy script reference, or provide the loaded Groovy script to the Spring context Other JavaBean references loaded in .

The Groovy script cache management unit 301 is specifically configured to read the Groovy script stored in the database into the cache.

The attached device also includes:

The grammar checking unit 304 is configured to check the grammar of the Groovy script before the BeanProcessor unit loads the Groovy script into the Spring context as a JavaBean, and determine that the grammar check of the Groovy script passes.

The syntax checking unit 304 is specifically used to determine whether the Groovy script includes at least one subclass inherited from the set base class, and when the judgment result is yes, determine that the syntax check of the Groovy script is passed; otherwise, It is determined that the syntax check of the Groovy script fails.

The BeanProcessor unit 303 is specifically configured to load the Groovy script as a JavaBean into the Spring context in a lazy loading manner.

The specific above-mentioned Groovy script loading device may be located in the Spring script loader.

Fig. 4 is the specific implementation structural diagram of the Spring script loader that the embodiment of the present application provides, as shown in Fig. 4, the Groovy script cache management unit in the Spring script loader reads the Groovy script in the database to the cache, and the SpringXML configuration assembly unit Obtain the attribute information of the Groovy script, and generate the corresponding XML configuration file and load it into the Spring context. The syntax checking unit checks whether the syntax of the Groovy script is wrong, and checks whether the Groovy script contains at least one child that inherits from the set base class. Class, if the check is passed, the BeanProcessor unit loads the Groovy script as a JavaBean into the Spring context in a lazy loading manner.

The embodiment of the present application provides a Groovy script loading method and device, in which the Spring script loader reads the Groovy script stored in the database, obtains the attribute information of the Groovy script, generates a corresponding XML configuration file and loads it into the Spring context, Finally, the Groovy script is loaded into the Spring context as a JavaBean. Since multiple JavaBeans under the Spring framework can refer to each other as needed, the Groovy script is loaded into the Spring context as a JavaBean in the embodiment of this application, so that the Groovy script can directly refer to the Other JavaBean, when other JavaBean needs to extend the function of the Groovy script, can also directly refer to the Groovy script which is also a JavaBean, thereby improving the scalability and flexibility of the Groovy script.

Obviously, those skilled in the art can make various changes and modifications to the application without departing from the spirit and scope of the application. In this way, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims (10)

1. A Groovy script loading method is characterized in that, comprising: The Spring script loader reads Groovy scripts stored in the database; and Obtain the attribute information of the Groovy script, generate a corresponding Extensible Markup Language XML configuration file according to the acquired attribute information, and load it into the Spring context; and Load the Groovy script as a JavaBean into the Spring context, and provide other JavaBean loaded in the Spring context to the loaded Groovy script reference, or provide the loaded Groovy script to other JavaBean references loaded in the Spring context . 2. The method according to claim 1, wherein the Spring script loader reads the Groovy script stored in the database, specifically comprising: The Spring script loader reads the Groovy script stored in the database into the cache. 3. the method as claimed in claim 1, is characterized in that, before described Groovy script is loaded in the Spring context as JavaBean, described method also comprises: A syntax check is performed on the Groovy script, and it is determined that the syntax check on the Groovy script passes. 4. The method according to claim 3, wherein the syntax checking of the Groovy script comprises: Judging whether the Groovy script contains at least one subclass inherited from the set base class; When the judgment result is yes, it is determined that the grammar check of the Groovy script passes; otherwise, it is determined that the grammar check of the Groovy script fails. 5. The method according to any one of claims 1 to 4, wherein the Groovy script is loaded into the Spring context as a JavaBean, specifically comprising: The Groovy script is loaded into the Spring context as a JavaBean in a lazy loading manner. 6. A Groovy script loading device, characterized in that, comprising: Groovy script cache management unit, used to read Groovy scripts stored in the database; The Spring Extensible Markup Language XML configuration assembly unit is used to obtain the attribute information of the Groovy script, generate a corresponding XML configuration file according to the obtained attribute information, and load it into the Spring context; The BeanProcessor unit is used to load the Groovy script as a JavaBean into the Spring context, and provide other JavaBean loaded in the Spring context to the loaded Groovy script reference, or provide the loaded Groovy script to the Spring context Other JavaBean references loaded. 7. The device according to claim 6, wherein the Groovy script cache management unit is specifically configured to read the Groovy script stored in the database into the cache. 8. The device of claim 6, further comprising: The syntax checking unit is used to check the syntax of the Groovy script before the BeanProcessor unit loads the Groovy script into the Spring context as a JavaBean, and determine that the syntax checking of the Groovy script passes. 9. The device according to claim 8, wherein the syntax checking unit is specifically used to determine whether at least one subclass inherited from the set base class is included in the Groovy script, and when the judgment result is yes , it is determined that the grammar check of the Groovy script passes, otherwise, it is determined that the grammar check of the Groovy script fails. 10. The device according to any one of claims 6-9, wherein the BeanProcessor unit is specifically configured to load the Groovy script as a JavaBean into the Spring context in a lazy loading manner.