CN103425462A

CN103425462A - Method and device for workflow data persistence

Info

Publication number: CN103425462A
Application number: CN2012101494230A
Authority: CN
Inventors: 章向明
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2012-05-14
Filing date: 2012-05-14
Publication date: 2013-12-04
Anticipated expiration: 2032-05-14
Also published as: CN103425462B

Abstract

The invention provides a method and device for workflow data persistence. The method includes extracting declared service information in configured files of a server terminal; establishing a dynamic proxy class for a declared server interface in the configured files of the server terminal, and generating strategy configured information of the server interface; acquiring target workflow data to be subject to persistence; transferring the server interface for workflow data persistence to acquire the dynamic proxy class, and assembling the target workflow data into an event in the dynamic proxy class; running the event according to the configured information of the workflow data persistence strategy, acquiring workflow data persistence server information corresponding to the event, and performing persistence on the target workflow data according to the workflow data persistence server information. By the aid of the method and device, maintaining cost can be saved, and scalability of workflow products can be enhanced.

Description

A kind of method and apparatus of Work stream data persistence

Technical field

The application relates to the technical field that Work stream data is processed, and particularly relates to a kind of device of method and a kind of Work stream data persistence of Work stream data persistence.

Background technology

Workflow (Work Flow) is exactly the computation model of workflow, is about to the logic organized together before and after the work how in workflow and rule is meaned with appropriate model in computing machine and to the calculation that in fact plays tricks.The subject matter that workflow will solve is: for realizing certain business objective, between a plurality of participants, utilize computing machine, by certain pre-defined rule, automatically transmit document, information or task.Briefly, workflow is exactly a series of mutual linkings, the business activity of automatically carrying out or task.Regard whole business procedure as Yi Tiaohe, the river wherein flow through is exactly workflow.

Workflow belongs to the part of computer supported cooperative work (Computer Supported Cooperative Work, CSCW).The latter studies a colony how under the help of computing machine, to realize collaborative work at large.

Many companies adopt the paper list, the manual mode of transmitting, and the one-level one-level is signed after examination, and work efficiency is very low, for the statistical report form function, can not realize.And the employing working flow software, the user only need fill in relevant list on computers, can automatically down run according to the flow process defined, and the next stage person of examining will receive related data, and can revise as required, follow the tracks of, manage, inquire about, add up, printing etc., greatly improved efficiency.

The persistence of Work stream data is a requisite ingredient of working flow products, the data persistence implementation of conventional operation miscarriage product, can't be flexibly without the various persistence demands that meet of invading, with JBPM3 commonly used in prior art, JBPM4 (Java Business Process Management, BPM) etc. product is example, it has realized a kind of mode of synchronous persistence Work stream data, based on described JBPM3, the products such as JBPM4, prior art has also proposed a kind of persistence mode of improved Work stream data, specifically comprise the steps:

Step 1: the code of the stream perdurable data that finds a job increases a judgment mechanism inside.

If find to have asynchronous sign in the flow process context, call asynchronous queue, do asynchronous perdurable data operation.If synchronous, direct invoke synchronous method.

Step 2: for example, when a new persistence demand is arranged: need to, according to the route of an appointment, call the asynchronous persistence flow data of remote server.Again change code this time, increase judgement and corresponding identifier.

Can find out, the form that the scheme of prior art is based on hard coded realizes, when increasing a kind of persistence mode, all needs to revise code.Increase the cost of safeguarding, be unfavorable for the expansion of business.

Therefore, those skilled in the art's technical matters in the urgent need to address is at present.How the mechanism of a kind of Work stream data persistence of creationary proposition, in order to save maintenance cost, strengthen the extendability of working flow products.

Summary of the invention

The application's purpose is to provide a kind of method and apparatus of Work stream data persistence, in order to improve the security of computing machine and the application of various user terminal, becomes those skilled in the art's problem in the urgent need to address.

In order to address the above problem, the application discloses a kind of method of Work stream data persistence, comprising:

Extract the information on services of stating in the service end configuration file; Wherein, described information on services comprises Work stream data persistence service information;

For the service interface of stating in the client configuration file creates the dynamic proxy class, and generate the tactful configuration information of described service interface; Wherein, described service interface comprises Work stream data persistence service interface, and described tactful configuration information comprises the tactful configuration information of Work stream data persistence;

Acquisition need to be carried out the target Work stream data of persistence;

Call described Work stream data persistence service interface and obtain its dynamic proxy class, and in described dynamic proxy class, described target Work stream data is assembled into to event;

Configuration information according to described Work stream data persistence strategy moves described event, obtain Work stream data persistence service information corresponding to described event, and according to described Work stream data persistence service information, the target Work stream data is carried out to the persistence operation.

Preferably, described Work stream data persistence service information comprises: service interface realize class, service interface is realized the address of class, service interface is realized the parameter type of stating in method in class and method;

After the step of the information on services of stating in described extraction service end configuration file, described method also comprises:

Described information on services is registered in the service end container according to the first preset data layout.

Preferably, described the first preset data layout comprises:

Service container and registration class ServiceRegistry, wherein, member variable comprises: mean the information on services set static Map<String that comprises various different names, ServiceInfo >;

The information ServiceInfo that service interface is realized, wherein, member variable comprises: service interface realize class, the service interface exposed, service interface is realized the address serviceURI of class, and service interface is realized the method information aggregate Map<String in class, OperationInfo >;

Service interface is realized the information OperationInfo of method in class, wherein, member variable comprises: the method name, the parameter information set List<ParameterInfo stated in method >, method rreturn value information ReturnInfo returnInfo) method abnormal information set List<ExceptionInfo >, method object (Method method);

The parameter information ParameterInfo stated in method, wherein, member variable comprises: parameter type String typeName, parameter type class Class type;

Method rreturn value information ReturnInfo, wherein, member variable comprises: rreturn value type String typeName, rreturn value class types Class type;

Method abnormal information ExceptionInfo, wherein, member variable comprises: Exception Type String typeName, Exception Type class Class type.

Preferably, after the service interface for stating in the client configuration file creates the step of dynamic proxy class, described method also comprises:

Described dynamic proxy class is registered in the client container.

Preferably, the configuration information of described Work stream data persistence strategy comprises:

When presentation of events occurs, the Event Policies eventName of the behavior act of execution;

While meaning storage information, adopt the storage policy storeRule of certain storage mode;

The routing policy routeRule that means the routing mechanism that message is transmitted;

The service that means the position at Interface realization class place realizes address endpointUrl;

The regulative strategy invokeType of the method for calling of presentation of events information;

And/or,

After meaning that message is consumed successfully, auto back is adjusted the loopback address callbackUri of initiator's address.

Preferably, described event is unified event; The described Work stream data persistence service interface that calls obtains its dynamic proxy class, and the step that the target Work stream data is assembled into to event in described dynamic proxy class comprises:

Call Work stream data persistence service interface from described client container;

By dynamic proxy class corresponding to described Work stream data persistence service interface interchange;

In described dynamic proxy class, realize the parameter type of stating in method in class and method according to described service interface, and the tactful configuration information of Work stream data persistence, be assembled into unified event by described target Work stream data according to the second preset data layout.

Preferably, described the second preset data layout comprises:

Unified event object UniformEvent: wherein, member variable comprises: sequence of events IDeventId, event title eventName, event call-back address callbackUri, event creation-time createdTime, event transmitting time sendedTime, on event with unified message object UniformMessage;

Unified message object UniformMessage: wherein, member variable comprises: message id messageId, and message header UniformMessageHeader, message body UniformMessagePlayload, Message Processing is rreturn value Object response as a result;

Unified message body object UniformMessagePlayload: wherein, member variable comprises: parameter list Object[] params;

A unified message object UniformMessageHeader: wherein, member variable comprises: the name eventName of event, event call-back address callbackUri, the time createdTime that message produces, message transmitting time sendedTime, service end realizes address endpointUrl, method name methodName, the time planTime of message plan consumption, storage rule storeRule, routing rule routeRule, time-out time timeout, failure number of retries retry, method of calling: synchronous/asynchronous invokeType.

Preferably, the described configuration information according to Work stream data persistence strategy moves described event, obtain Work stream data persistence service information corresponding to described event, and the step of the target Work stream data being carried out to the persistence operation according to described Work stream data persistence service information comprises:

Obtain the method for calling according to message in the event of described regulative strategy configuration, if synchronization call triggers described event, described event has the event title;

Realize class according to the corresponding action listener of described event name acquiring, described action listener realizes that class is according to described Event Policies configuration integrate;

In described action listener is realized class, according to described routing policy, search the address that the service interface that is positioned at Local or Remote is realized class;

Realize the address of class according to described service interface, from the service end container, find corresponding service interface to realize class;

Call described service interface and realize class, described target Work stream data is kept in the workflow database of Local or Remote.

Preferably, before calling described Work stream data persistence service interface, described method also comprises:

Start affairs in default task manager;

The described configuration information according to Work stream data persistence strategy moves described event, obtain Work stream data persistence service information corresponding to described event, and the step of the target Work stream data being carried out to the persistence operation according to described Work stream data persistence service information comprises:

Obtain the method for calling according to message in the event of described regulative strategy configuration, if asynchronous call creates the transactional synchronization device, and in described task manager the registration transactions synchronizer;

Submit affairs to, call the transactional synchronization device, the message according in described storage policy preservation event, then add event in asynchronous queue;

When asynchronous queue's audiomonitor has listened to event and adds, trigger described event;

Realize class according to the corresponding action listener of the name acquiring of described event, described action listener realizes that class is according to described Event Policies configuration integrate;

Call described service interface and realize class, described target Work stream data is kept in the workflow database of Local or Remote;

If described service interface is realized class and is called successfully, according to described storage policy, delete the event message of preserving, then according to described loopback address, the readjustment initiator notifies and operates successfully;

If described service interface is realized the class malloc failure malloc, according to described loopback address, the readjustment initiator carries out the compensation business operation.

Preferably, the step that described acquisition need to be carried out the target Work stream data of persistence comprises:

Flow instance starts circulation, runs into the node that needs save data, the data of node instance is saved in the ordered queue of appointment in the flow process context;

The flow instance circulation finishes, and the node instance data of obtaining in described ordered queue are the target Work stream data that need to carry out persistence.

The embodiment of the present application also discloses a kind of device of Work stream data persistence, comprising:

The service end configuration module, the information on services of stating for extracting the service end configuration file; Wherein, described information on services comprises Work stream data persistence service information;

The client configuration module, be used to the service interface of stating in the client configuration file to create the dynamic proxy class, and generate the tactful configuration information of described service interface; Wherein, described service interface comprises Work stream data persistence service interface, and described tactful configuration information comprises the tactful configuration information of Work stream data persistence;

The Work stream data acquisition module, for obtaining the target Work stream data that need to carry out persistence;

The proxy class calling module, obtain its dynamic proxy class for calling described Work stream data persistence service interface, and in described dynamic proxy class, described target Work stream data be assembled into to event;

The event execution module, move described event for the configuration information according to described Work stream data persistence strategy, obtain Work stream data persistence service information corresponding to described event, and according to described Work stream data persistence service information, the target Work stream data is carried out to the persistence operation.

Described device also comprises:

The service container Registering modules, be connected with described service end configuration module, for described information on services is registered to the service end container according to the first preset data layout.

Preferably, described the first preset data layout comprises:

Preferably, described device also comprises:

Client container Registering modules, be connected with described client configuration module, for described dynamic proxy class is registered to the client container.

And/or,

Preferably, described event is unified event; Described proxy class calling module comprises:

Service interface calls submodule, for from described client container, calling Work stream data persistence service interface;

The dynamic proxy class is extracted submodule, for by dynamic proxy class corresponding to described Work stream data persistence service interface interchange;

Event assembling submodule, be used in described dynamic proxy class, realize the parameter type of stating in method in class and method according to described service interface, and, the tactful configuration information of Work stream data persistence, be assembled into unified event by described target Work stream data according to the second preset data layout.

Preferably, described the second preset data layout comprises:

Preferably, described event execution module comprises:

The first Event triggered submodule, for obtaining the method for calling according to the event message of described regulative strategy configuration, if synchronization call triggers described event, described event has the event title;

The action listener submodule, for according to the corresponding action listener of described event name acquiring, realizing class, described action listener realizes that class is according to described Event Policies configuration integrate;

The route submodule, at described action listener, realizing class, according to described routing policy, search the address that the service interface that is positioned at Local or Remote is realized class;

Realize class locator module, for realize the address of class according to described service interface, from the service end container, find corresponding service interface to realize class;

Persistence operation submodule, realize class for calling described service interface, and described target Work stream data is kept in the workflow database of Local or Remote.

Preferably, described device also comprises:

Affairs start module, for the task manager default, start affairs;

Described event execution module comprises:

The transactional synchronization device creates submodule, for obtaining the method for calling according to the event message of described regulative strategy configuration, if asynchronous call creates the transactional synchronization device, and in described task manager the registration transactions synchronizer;

The transaction commitment processing submodule, for submitting affairs to, call the transactional synchronization device, and the message according in described storage policy preservation event, then add event in asynchronous queue;

Second event triggers submodule, when for asynchronous queue's audiomonitor, having listened to event and add, triggers described event;

The action listener submodule, realize class for the corresponding action listener of the name acquiring according to described event, and described action listener realizes that class is according to described Event Policies configuration integrate;

Persistence operation submodule, realize class for calling described service interface, and described target Work stream data is kept in the workflow database of Local or Remote;

Call and successfully process submodule, for when described service interface realizes that class is called successfully, according to described storage policy, delete the event message of preserving, then according to described loopback address, the readjustment initiator notifies and operates successfully;

Malloc failure malloc is processed submodule, and at described service interface, realizing the class malloc failure malloc, according to described loopback address, the readjustment initiator carries out the compensation business operation.

Preferably, described Work stream data acquisition module comprises:

Data generate submodule, for flow instance, start circulation, run into the node that needs save data, the data of node instance are saved in the ordered queue of appointment in the flow process context;

Data are extracted submodule, for the flow instance circulation, finish, and the node instance data of obtaining in described ordered queue are the target Work stream data that need to carry out persistence.

Compared with prior art, the application comprises following advantage:

The application has proposed a kind of brand-new Work stream data persistence strategy Configuration Framework, situation according to the workflow business, as while increasing a kind of persistence mode, without revising code, only need the simple modification configuration file, can freely select Event Policies, the message stores strategy, routing policy, the strategy of the Work stream data persistences such as regulative strategy is realized the preservation of Work stream data, thereby can save maintenance cost, strengthen the extendability of working flow products.

The accompanying drawing explanation

Fig. 1 is the workflow schematic diagram that the loaning bill business is example of going on business;

Fig. 2 is the flow chart of steps of embodiment of the method for a kind of Work stream data persistence of the application;

Fig. 3 is the process flow diagram of the concrete example carried out of a kind of Work stream data persistence method of application the embodiment of the present application;

Fig. 4 is the structured flowchart of device embodiment of a kind of Work stream data persistence of the application.

Embodiment

For above-mentioned purpose, the feature and advantage that make the application can become apparent more, below in conjunction with the drawings and specific embodiments, the application is described in further detail.

For making those skilled in the art understand better the application, below with " loaning bill of going on business " this concrete business, the related notion term that the application relates to is described.

With reference to the process flow diagram of the loaning bill business of going on business shown in figure 1, when the employee goes on business, can be used for buying ticket to corporate loans in advance, the expenses such as board and lodging.Company regulation, the employee goes on business the amount of money of loan application while being less than or equal to 5000 yuans, needs supervisor to examine, and after supervisor examines, needs financial approval, finally fund is beaten to money in employee's wage card by bank.If the amount of money that the employee borrows money is greater than 5000 yuans, need supervisor to examine, after supervisor examines, need manager again to examine, after examining, manager needs financial approval, finally fund is beaten to money in employee's wage card by bank.If supervisor, manager or financial approval are disagreed with, need to send out mail and inform the employee.

Terminological interpretation is as follows:

Node: refer to some business activity definition.In this example, " financial approval " is exactly a node, and this node needs the people to participate in, and is referred to as task node." money is beaten by bank " is also a node, and this node participates in without the people, is referred to as automatic node.Node shows with the rectangle frame table in Fig. 1." judgement borrowing balance " this activity, be used for judging flow process from which branch continues after this node, is referred to as decision node.

Directed connection: refer in Fig. 1 the line with arrow, mean flow process from a state by which kind of mode to another state.As in this example, manager examines node between the financial approval node, has one and cry the directed connection of " agreement ".

Flow definition: be that symbol for describing some operation flows means, the static defining file formed by node and directed connection.

Above term is all the concept of flow process configuration class, below introduces the related notion during process flow operation.

Active instance: refer to certain once node instance of concrete service request process.For example: Xiao Wang plans on October 15th, 2010 and goes to Beijing to go on business, 7000 yuan of loan applications.Xiao Wang is in 9 o'clock sharps of the morning on October 14th, 2010, submit applications flow process in Workflow system.Be responsible for 10 o'clock sharps of the morning on October 14th, 2010 and examine, then flow process continues to walk downward.Wherein, describing " supervisor examines " this movable example is active instance.Usually active instance comprises this activity start time, concluding time, plan handler, actual treatment people, the information of subscription time etc. different dimensions.

Flow instance: refer to certain once concrete service request.For example: Xiao Wang goes to Beijing to go on business on October 15th, 2010,7000 yuan of loan applications.Flow instance is comprised of a series of active instance.In the flow instance of this example indication, if finally examine agreement, comprise start node " application of going on business " active instance, " supervisor examines " active instance, " judgement borrowing balance " active instance, " manager examines " active instance, " financial approval " active instance, " money is beaten by bank " active instance, " end " active instance.

Flow process context variable example: refer to that certain is once in concrete service request, for the data of transmission of information between node.Be generally the form performance of name-value pair (key-value).General context variable example refers to each flow instance, no matter whether belongs to same flow definition, the context variable example all had.The context variable example is usually referred to as context variable.

One of core idea of the embodiment of the present application is, a kind of situation according to the workflow business of creationary proposition, only need the simple modification configuration file, can freely select Event Policies, the message stores strategy, routing policy, the strategy of the Work stream data persistences such as regulative strategy, with the mechanism that realizes that Work stream data is preserved.

With reference to Fig. 2, show the flow chart of steps of embodiment of the method for a kind of Work stream data persistence of the application, specifically can comprise the steps:

Step 201, extract the information on services of stating in the service end configuration file;

Wherein, described information on services comprises Work stream data persistence service information.

In specific implementation, described Work stream data persistence service information can comprise: service interface realize class, service interface is realized the address of class, service interface is realized the parameter type of stating in method in class and method.It should be noted that, the parameter type of stating in described method does not refer to concrete data, and refers to that service interface realizes that the method in class receives the parameter of what type, is the statement of parameter type.

In a preferred embodiment of the present application, after described step 201, can carry out following steps:

Step 202, be registered to described information on services in the service end container according to the first preset data layout.

In specific implementation, when system starts, can configure XML (the service end configuration file is generally the XML file) according to service end, by the service registry stated in XML in the service end container.According to service end configuration XML, by the service registry stated in XML in service container.

As a kind of example of the concrete application of the embodiment of the present application, described the first preset data layout can comprise following content:

Certainly, the data layout of above-mentioned service end container is only as example, and it is all feasible that those skilled in the art adopt any data layout according to the actual requirements, the application to this without being limited.

Step 203, for the service interface of stating in the client configuration file creates the dynamic proxy class, and generate the tactful configuration information of described service interface;

Wherein, described service interface can comprise Work stream data persistence service interface, and described tactful configuration information can comprise the tactful configuration information of Work stream data persistence.Described information on services and service interface have corresponding relation, and described Work stream data persistence service information is corresponding with Work stream data persistence service interface.

The dynamic proxy class is to utilize the reflex mechanism of java to generate.Having comprised the support to dynamic proxy in current Java kit. it is realized mainly by being java.lang.reflect.Proxy class and java.lang.reflect.InvocationHandler interface.

The Proxy class is mainly used to obtain the dynamic proxy object, the InvocationHandler interface is used for retraining caller and realizes, as follows, the operational approach of HelloWorld interface definition, HelloWorldImpl is the realization of HelloWorld interface, and HelloWorldHandler is the InvocationHandler Interface realization.Code is as follows:

Business interface:

public interface HelloWorld{

void sayHelloWorld()；

}

Business interface is realized:

The InvocationHandler realization need to add a part of work for the treatment of before and after calling interface method, only before and after method call, to backstage, exports two character strings here, and its code is as follows:

Test code:

At first obtain the object of realizing of a business interface;

Obtain an InvocationHandler and realize, be the HelloWorldHandler object herein;

Create the dynamic proxy object;

By dynamic proxy object reference sayHelloWorld () method, now can before and after primary object HelloWorldImpl.sayHelloWorld () method, export two character strings.

The output of operation test class is as follows:

before method invoke！

Hello World！

after method invoke！

Method call code in the Test class is many herein, can simplify by configuration file the realization of calling of client in actual applications.

In specific implementation, can be according to client configuration XML (client configuration file, be generally the XML file), for the service interface of stating in XML creates the dynamic proxy class, and configuration event strategy eventName, storage policy storeRule, routing policy routeRule, service realizes address endpointUrl, regulative strategy invokeType, the strategy of the Work stream data persistences such as loopback address callbackUri.

Particularly, the strategy of described Work stream data persistence can comprise:

And/or,

Certainly, above-mentioned strategy configuration is only as example, and it is all feasible that those skilled in the art adopt any strategy configuration according to the actual requirements, the application to this without being limited.

In a preferred embodiment of the present application, after described step 103, can carry out following steps:

Step 204, be registered to described dynamic proxy class in the client container.

In specific implementation, after being registered in the client container by the dynamic proxy class, in the follow-up use of client, can directly obtain from container.

Step 205, acquisition need to be carried out the target Work stream data of persistence;

As a kind of example of the concrete application of the embodiment of the present application, described step 205 can comprise following sub-step:

Sub-step S11, flow instance start circulation, run into the node that needs save data, the data of node instance are saved in the ordered queue of appointment in the flow process context;

Sub-step S12, flow instance circulation finish, and the node instance data of obtaining in described ordered queue are the target Work stream data that need to carry out persistence.

Step 206, call described Work stream data persistence service interface and obtain its dynamic proxy class, and in described dynamic proxy class, described target Work stream data is assembled into to event;

In specific implementation, can before calling described Work stream data persistence service interface, in default task manager, start affairs, call the local service database manipulation, and then call Work stream data persistence service interface.Wherein, described affairs refer to the local service db transaction,, take and go on business loan application as example, wherein, the place of going on business, time, number of days, the list of going on business that the origin of an incident forms, be exactly business datum, calls the business datum that the local service database manipulation refers to preserve the list of going on business.

In a preferred embodiment of the present application, described event is unified event; Described step 206 specifically can comprise following sub-step:

Sub-step S21, call Work stream data persistence service interface from described client container;

Sub-step S22, by dynamic proxy class corresponding to described Work stream data persistence service interface interchange;

Sub-step S23, in described dynamic proxy class, realize the parameter type of stating in method in class and method according to described service interface, and the tactful configuration information of Work stream data persistence, be assembled into unified event by described target Work stream data according to the second preset data layout.

Below call by a simple example explanation principle that described Work stream data persistence service interface obtains its dynamic proxy class:

Call the com.ali.xbpm.eda.test.EdaWorkflowService interface in the flow engine category-A.One section code in category-A is as follows:

EdaWorkflowService workflowClient＝ (EdaWorkflowService)ContextFactory

.get(“workflowClient”)；

workflowClient.storeProcess(bpmProcInst，contextMap，queue)

In the epimere code, can find, this workflow persistence service interface of EdaWorkflowService, by obtaining in client container C ontextFactory.Owing to passing through client configuration, for this service interface has created the dynamic proxy class.So what obtain from ContextFactory is the dynamic proxy class, but not real service interface is realized class.

Because the dynamic proxy class is according to the client configuration file, utilize the reflex mechanism of java to generate.It is actually of interface and realizes class.In the process generated at the reflex mechanism that utilizes java, just the tactful configuration information of Work stream data persistence (being various strategy configurations) is read into, be kept in the member variable of dynamic proxy class.Also because the dynamic proxy class, be exactly that another of interface realized class in fact, so can receive the data that service interface is realized the parameter type stated in method in class and method.

Below by the method for reflection of one section code description java:

Method in Java Method class:

java.lang.reflect.Method.invoke(Object obj，Object... args)throwsIllegalAccessException， IllegalArgumentException，InvocationTargetException

Wherein, obj is exactly the interface class name, and args is actual parameter list.

As a kind of example of the concrete application of the embodiment of the present application, described the second preset data layout can comprise:

Certainly, the assemble method of above-mentioned event is only as example, and it is all feasible that those skilled in the art adopt any assemble method according to the actual requirements, the application to this without being limited.

Step 207, configuration information according to described Work stream data persistence strategy moves described event, obtain Work stream data persistence service information corresponding to described event, and according to described Work stream data persistence service information, the target Work stream data is carried out to the persistence operation.

In a preferred embodiment of the present application, described step 207 can comprise following sub-step:

Sub-step S31, obtain the method for calling according to message in the event of described regulative strategy configuration, if synchronization call triggers described event, described event has the event title;

Sub-step S32, according to the corresponding action listener of described event name acquiring, realize class, described action listener realizes that class is according to described Event Policies configuration integrate;

Sub-step S33, in described action listener is realized class, according to described routing policy, search the address that the service interface that is positioned at Local or Remote is realized class;

Sub-step S34, the address of realizing class according to described service interface find corresponding service interface to realize class from the service end container;

Sub-step S35, call described service interface and realize class, described target Work stream data is kept in the workflow database of Local or Remote.

In another preferred embodiment of the present application, described step 207 can comprise following sub-step:

Sub-step S41, obtain the method for calling according to message in the event of described regulative strategy configuration, if asynchronous call creates the transactional synchronization device, and in described task manager the registration transactions synchronizer;

Utilize the transactional synchronization device, purpose can have consistent affairs for the Work stream data that guarantees local service data and (Local or Remote) exactly.

Sub-step S42, submission affairs, call the transactional synchronization device, and the message according in described storage policy preservation event, then add event in asynchronous queue;

When sub-step S43, asynchronous queue's audiomonitor have listened to event and add, trigger described event;

Sub-step S44, according to the corresponding action listener of the name acquiring of described event, realize class, described action listener realizes that class is according to described Event Policies configuration integrate;

Sub-step S45, in described action listener is realized class, according to described routing policy, search the address that the service interface that is positioned at Local or Remote is realized class;

Sub-step S46, the address of realizing class according to described service interface find corresponding service interface to realize class from the service end container;

Sub-step S47, call described service interface and realize class, described target Work stream data is kept in the workflow database of Local or Remote;

If the described service interface of sub-step S48 is realized class and is called successfully, according to described storage policy, delete the event message of preserving, then according to described loopback address, the readjustment initiator notifies and operates successfully;

If the described service interface of sub-step S49 is realized the class malloc failure malloc, according to described loopback address, the readjustment initiator carries out the compensation business operation.

For making those skilled in the art understand better the embodiment of the present application, carry out the process flow diagram of Work stream data persistence operation below in conjunction with the application the embodiment of the present application shown in Fig. 3, by a concrete example, further illustrate.

Step 1: according to service end configuration XML, by the service registry stated in XML to (step 1 in Fig. 3 (1)) in service container (being the service end container).

Wherein, the data layout of service end container comprises:

ServiceRegistry class: service end container and registration class

Member variable: static Map<String, ServiceInfo >, mean the information on services set that comprises various different names.

ServiceInfo information on services: describe the information that service interface is realized.

Member variable: the supplier of service (being the class that realizes of interface), the service interface (can be a plurality of interfaces) exposed, the address (String type serviceURI) of service, the method information aggregate (Map<String, OperationInfo >).

OperationInfo method information: the information of describing method.

Member variable: method name, the method parameter information aggregate (List<ParameterInfo >), method rreturn value information (ReturnInfo returnInfo), the set of method abnormal information (List<ExceptionInfo >), method object (Method method).

ParameterInfo method parameter information: the information of describing method parameter.

Member variable: parameter type (String typeName), parameter type class (Class type)

ReturnInfo method rreturn value information: the rreturn value information of describing method.

Member variable: rreturn value type (String typeName), rreturn value class types (Class type)

ExceptionInfo method abnormal information: the abnormal information of describing method.

Member variable: Exception Type (String typeName), Exception Type class (Class type)

The example code of the service end configuration file that a kind of the embodiment of the present application used in specific implementation below is provided:

Step 2: according to client configuration XML, for the interface of stating in XML creates dynamic proxy, configuration event strategy eventName, storage policy storeRule, routing policy routeRule, service realizes address endpointUrl, regulative strategy invokeType, loopback address callbackUri.(step 1 in Fig. 3 (2))

Wherein, Event Policies: when presentation of events occurs, the behavior act of execution.Comprise the local method call event, long-range mina calls event etc.

Storage policy: while meaning storage information, adopt which kind of storage mode.Comprise the berkeleyDb storage, mysql storage etc.

Routing policy: mean the routing mechanism that message is transmitted.For example: circulation in local Java Virtual Machine, the circulation of long-range flow process center.

Service realizes address: the position that means Interface realization class place.Can be local, can be also long-range.

Regulative strategy: the method for calling of presentation of events information.For example: synchronization call (sync), asynchronous call (async), asynchronous reliably call (asyncrely) etc.

Loopback address: after meaning that message is consumed successfully, auto back is adjusted initiator's address.

The example code of the client configuration file that a kind of the embodiment of the present application used in specific implementation below is provided:

Step 3: flow instance starts circulation, runs into the node that needs save data, and node instance (being active instance) data are saved in the ordered queue of appointment in the flow process context.(step 3,4 in Fig. 3)

Step 4: the flow instance circulation finishes.Start to start affairs, call the local service database manipulation, and then call Work stream data persistence service interface.This interface is exactly the interface of stating in step 2.It is actual that what call is the dynamic proxy class of interface.Described Work stream data persistence service interface gets corresponding node instance data from the contextual ordered queue of described flow process.(step 5,6,7,8,9 in Fig. 3)

Step 5: in the dynamic proxy class, according to the method for interface, parameter, be assembled into unified event.(step 10 in Fig. 3)

The data structure of unified event is as follows:

UniformEvent: unified event is to support successor strategy, routing policy, message stores strategy, the carrier object of regulative strategy.Event object does not transmit when cross-system calls.

Member variable has: sequence of events ID (eventId), name (the eventName of event, the successor strategy determines according to this title), event call-back URI (callbackUri, be the loopback address after message success or failure), event creation-time (createdTime), event transmitting time (sendedTime), on event with message object (UniformMessage).

UniformMessage: unified message is used for cross-system to transmit the carrier of data.

Member variable has: message id (messageId), and message header (UniformMessageHeader), message body (UniformMessagePlayload), Message Processing is rreturn value (Object response) as a result.

UniformMessagePlayload: unified message body object.

Member variable has: parameter list (Object[] params)

UniformMessageHeader: a unified message object.

Member variable has: the name of event [eventName], event call-back URI[callbackUri], the time [createdTime] that message produces, message transmitting time [sendedTime], service end realizes address [endpointUrl], method name [methodName], the time [planTime] of message plan consumption, storage rule [storeRule], routing rule [routeRule], time-out time [timeout], failed number of retries [retry], method of calling: synchronous/asynchronous [invokeType].

Take and go on business loan application as example.After flow instance starts, through start node, after examining node, supervisor enters waiting status.Now called workflow persistence service interface and preserved Work stream data, example code is as follows:

EdaWorkflowService workflowClient＝ (EdaWorkflowService)ContextFactory

.get(“workflowClient”)；

workflowClient.storeProcess(bpmProcInst，contextMap，queue)

Parameter list has: flow instance bpmProcInst, context Map data contextMap, be active instance data (supervisor examines the active instance data of node) in the queue queue

The unified event object of assembling is as follows:

Step 6: according to the method for calling (being regulative strategy) of message in event, call event engine scheduling class.(step 11 in Fig. 3)

If synchronization call, trigger event, according to concrete event title, call different action listeners and realize class (being Event Policies) (step 12,13 in Fig. 3).Then go to step nine.

If asynchronous call creates the transactional synchronization device, and in task manager registration transactions synchronizer (step 12,12.1,12.2 in Fig. 3).Then go to step seven.

Step 7, submit affairs to, call the transactional synchronization device, the message in the preservation event is (according to the storing message strategy, can select mysql and berkeleydb to carry out the storage of message), then event is added (step 13,14,15,16 in Fig. 3) in asynchronous queue.

Step 8, asynchronous queue's audiomonitor, the event of having listened to adds, trigger event.According to concrete event title, call different action listeners and realize class) be Event Policies) (step 17 in Fig. 3).

Step 9, realize in class at action listener, according to routing policy, finds the service implementing type address (step 14 in Fig. 3 (18)) of Local or Remote.

Step 10 according to the service implementing type address, finds the interface of registering really to realize class from the service end container.Then call this and realize class persistence Work stream data, Work stream data is saved in the workflow database of Local or Remote (step 15 in Fig. 3 (19), 16 (20)).

Step 11: after calling successfully, if method of calling is asynchronous, according to storage policy, delete the event message of preserving.Then according to loopback address, auto back has been readjusted the distribution square tube and has been known successfully; After malloc failure malloc, according to loopback address, auto back adjusts the initiator to do compensation business operation (step 21,22 in Fig. 3).

Below provide one section to realize the example code of above-mentioned steps six to step 11:

Application the embodiment of the present application, can be according to the situation of workflow business, only need the simple configuration file of revising, can freely select Event Policies, the message stores strategy, routing policy, the Work stream data persistence service strategies such as regulative strategy, save maintenance cost, greatly strengthened the extendability of working flow products.

It should be noted that, for embodiment of the method, for simple description, therefore it all is expressed as to a series of combination of actions, but those skilled in the art should know, the application is not subject to the restriction of described sequence of movement, because according to the application, some step can adopt other orders or carry out simultaneously.Secondly, those skilled in the art also should know, the embodiment described in instructions all belongs to preferred embodiment, and related action and module might not be that the application is necessary.

With reference to Fig. 4, show the structured flowchart of device embodiment of a kind of Work stream data persistence of the application, specifically can comprise as lower module:

Service end configuration module 401, the information on services of stating for extracting the service end configuration file; Wherein, described information on services comprises Work stream data persistence service information;

Client configuration module 402, be used to the service interface of stating in the client configuration file to create the dynamic proxy class, and generate the tactful configuration information of described service interface; Wherein, described service interface comprises Work stream data persistence service interface, and described tactful configuration information comprises the tactful configuration information of Work stream data persistence;

Work stream data acquisition module 403, for obtaining the target Work stream data that need to carry out persistence;

Proxy class calling module 404, obtain its dynamic proxy class for calling described Work stream data persistence service interface, and in described dynamic proxy class, described target Work stream data be assembled into to event;

Event execution module 405, move described event for the configuration information according to described Work stream data persistence strategy, obtain Work stream data persistence service information corresponding to described event, and according to described Work stream data persistence service information, the target Work stream data is carried out to the persistence operation.

In specific implementation, described Work stream data persistence service information can comprise: service interface realize class, service interface is realized the address of class, service interface is realized the parameter type of stating in method in class and method;

In a preferred embodiment of the present application, described device can also comprise as lower module:

The service container Registering modules, be connected with described service end configuration module 401, for described information on services is registered to the service end container according to the first preset data layout.

As a kind of example of the concrete application of the embodiment of the present application, the configuration information of described Work stream data persistence strategy can comprise:

And/or,

In specific implementation, described event is unified event; Described proxy class calling module 404 can comprise following submodule:

As a kind of example of the concrete application of the embodiment of the present application, described the second preset data layout can comprise following content:

In a preferred embodiment of the present application, described event execution module 405 can comprise following submodule:

As another preferred embodiment of the present application, described device can also comprise that affairs start module, start affairs for the task manager default;

In this case, described event execution module 405 can comprise following submodule:

In specific implementation, described Work stream data acquisition module 403 comprises:

For device embodiment, because it is substantially similar to embodiment of the method, so description is fairly simple, relevant part gets final product referring to the part explanation of embodiment of the method.

Those skilled in the art should understand, the application's embodiment can be provided as method, system or computer program.Therefore, the application can adopt complete hardware implementation example, implement software example or in conjunction with the form of the embodiment of software and hardware aspect fully.And the application can adopt the form that wherein includes the upper computer program of implementing of computer-usable storage medium (including but not limited to magnetic disk memory, CD-ROM, optical memory etc.) of computer usable program code one or more.

The application describes with reference to process flow diagram and/or the block scheme of method, equipment (system) and computer program according to the embodiment of the present application.Should understand can be in computer program instructions realization flow figure and/or block scheme each flow process and/or the flow process in square frame and process flow diagram and/or block scheme and/or the combination of square frame.Can provide these computer program instructions to the processor of multi-purpose computer, special purpose computer, Embedded Processor or other programmable data processing device to produce a machine, make the instruction of carrying out by the processor of computing machine or other programmable data processing device produce for realizing the device in the function of flow process of process flow diagram or a plurality of flow process and/or square frame of block scheme or a plurality of square frame appointments.

These computer program instructions also can be stored in energy vectoring computer or the computer-readable memory of other programmable data processing device with ad hoc fashion work, make the instruction be stored in this computer-readable memory produce the manufacture that comprises command device, this command device is realized the function of appointment in flow process of process flow diagram or a plurality of flow process and/or square frame of block scheme or a plurality of square frame.

These computer program instructions also can be loaded on computing machine or other programmable data processing device, make and carry out the sequence of operations step to produce computer implemented processing on computing machine or other programmable devices, thereby the instruction of carrying out on computing machine or other programmable devices is provided for realizing the step of the function of appointment in flow process of process flow diagram or a plurality of flow process and/or square frame of block scheme or a plurality of square frame.

Although described the application's preferred embodiment, once those skilled in the art obtain the basic creative concept of cicada, can make other change and modification to these embodiment.So claims are intended to all changes and the modification that are interpreted as comprising preferred embodiment and fall into the application's scope.

Finally, also it should be noted that, in this article, relational terms such as the first and second grades only is used for an entity or operation are separated with another entity or operational zone, and not necessarily requires or imply between these entities or operation the relation of any this reality or sequentially of existing.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thereby make the process, method, article or the equipment that comprise a series of key elements not only comprise those key elements, but also comprise other key elements of clearly not listing, or also be included as the intrinsic key element of this process, method, article or equipment.In the situation that not more restrictions, the key element limited by statement " comprising ... ", and be not precluded within process, method, article or the equipment that comprises described key element and also have other identical element.

The method of above a kind of Work stream data persistence that the application is provided and a kind of device of Work stream data persistence are described in detail, applied specific case herein the application's principle and embodiment are set forth, the explanation of above embodiment is just for helping to understand the application's method and core concept thereof; Simultaneously, for one of ordinary skill in the art, the thought according to the application, all will change in specific embodiments and applications, and in sum, this description should not be construed as the restriction to the application.

Claims

1. the method for a Work stream data persistence, is characterized in that, comprising:

Acquisition need to be carried out the target Work stream data of persistence;

2. method according to claim 1, is characterized in that, described Work stream data persistence service information comprises: service interface realize class, service interface is realized the address of class, service interface is realized the parameter type of stating in method in class and method;

3. method according to claim 2, is characterized in that, described the first preset data layout comprises:

4. method according to claim 1, is characterized in that, after the service interface for stating in the client configuration file creates the step of dynamic proxy class, described method also comprises:

Described dynamic proxy class is registered in the client container.

5. method according to claim 4, is characterized in that, the configuration information of described Work stream data persistence strategy comprises:

And/or,

6. according to the method in claim 2 or 3, it is characterized in that, described event is unified event; The described Work stream data persistence service interface that calls obtains its dynamic proxy class, and the step that the target Work stream data is assembled into to event in described dynamic proxy class comprises:

7. method according to claim 6, is characterized in that, described the second preset data layout comprises:

8. according to the described method of claim 3 or 7, it is characterized in that, the described configuration information according to Work stream data persistence strategy moves described event, obtain Work stream data persistence service information corresponding to described event, and the step of the target Work stream data being carried out to the persistence operation according to described Work stream data persistence service information comprises:

9. according to the described method of claim 3 or 7, it is characterized in that, before calling described Work stream data persistence service interface, described method also comprises:

Start affairs in default task manager;

10. method according to claim 1, is characterized in that, the step that described acquisition need to be carried out the target Work stream data of persistence comprises:

11. the device of a Work stream data persistence, is characterized in that, comprising:

12. device according to claim 11, is characterized in that, described Work stream data persistence service information comprises: service interface realize class, service interface is realized the address of class, service interface is realized the parameter type of stating in method in class and method;

Described device also comprises:

13. device according to claim 12, is characterized in that, described the first preset data layout comprises:

Service container and registration class ServiceRegistfy, wherein, member variable comprises: mean the information on services set static Map<String that comprises various different names, ServiceInfo >;

14. device according to claim 11, is characterized in that, also comprises:

15. device according to claim 14, is characterized in that, the configuration information of described Work stream data persistence strategy comprises:

And/or,

16. according to the described device of claim 12 or 13, it is characterized in that, described event is unified event; Described proxy class calling module comprises:

17. device according to claim 16, is characterized in that, described the second preset data layout comprises:

Unified event object UniformEvent: wherein, member variable comprises: sequence of events ID eventId, event title eventName, event call-back address callbackUri, event creation-time createdTime, event transmitting time sendedTime, on event with unified message object UniformMessage;

18. according to the described device of claim 13 or 17, it is characterized in that, described event execution module comprises:

19. according to the described device of claim 13 or 17, it is characterized in that, also comprise:

Affairs start module, for the task manager default, start affairs;

Described event execution module comprises:

20. device according to claim 11, is characterized in that, described Work stream data acquisition module comprises: