CN100498717C

CN100498717C - Method for calling enterprise grade Java assembling method

Info

Publication number: CN100498717C
Application number: CNB2004100582545A
Authority: CN
Inventors: 卡辛克·M; K·尤岱·金史尔; 杰立·库澜
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2004-08-20
Filing date: 2004-08-20
Publication date: 2009-06-10
Anticipated expiration: 2024-08-20
Also published as: CN1737762A

Abstract

This invention discloses one enterprise Java parts dispatching method, which declares asynchronism method in the description files and also comprises the following steps: a, sending the requirement of transferring aim EJB method into KJB frame by customer end through application program; b, the EJB frame judges the aim description files whether the customer terminal used aim is asynchronism method, if yes, then executing step c; if not, then executing simultaneous method and closing the local process; c, EJB establishing one asynchronism transferring subject; d, the EJB container dispatches the aim KJB asynchromism method.

Description

A kind of method that the method for enterprise-level Java assembly is called

Technical field

The present invention relates to the Java technology, particularly relate to a kind of method that the method for enterprise-level Java assembly is called.

Background technology

In the Java technology, assembly (Bean) is a reusable Java module based on Java software assembly model (JavaBeans).In Bean, method is a code module, generates the behavior of an object instance, and with procedural programming language in functional similarity.In order to define a method, the supplier of Bean must state this method, realize its main body then.And the attribute of Bean can be obtained and be provided with to client by the method for calling Bean, and finish the various operations to Bean.

Enterprise-level Java Bean (EJB, Enterprise Java Bean) is an assembly of realizing the server end application service.The EJB framework is the containment system that supports EJB, is a kind of assembly type framework of the develop and field of using at the object-oriented distributed business.Use the application of EJB framework exploitation, have good retractility, issued transaction and multi-user's security reliably, and these are only used and need exploitation once, can be deployed to the server platform of any support EJB standard.

The EJB framework can be realized following parts flexibly:

A kind of representative stateless service object; A kind of representative stateless service object realizes World Wide Web (WEB) service terminal (endpoint); A kind of representative stateless service object, the asynchronous call that gives information and drive; A kind of object of representing client session is safeguarded the session status of a plurality of client call methods automatically; A kind of entity object, representative can be by the shared business object of a plurality of clients; A kind of entity object is represented the persistent storage object of a kind of hachure (fine-grained), has wherein comprised the persistent storage state of corresponding thick lines (coarse-grained) business object.

At These characteristics, the EJB architecture definition three types EJB: session Bean (SessionBean), entity B ean (Entity Bean) and message-driven Bean (MDB, Message-drivenBean).And, EJB framework regulation, the method for session Bean and entity B ean is a method for synchronous, promptly all are synchronous to calling of session Bean or entity B ean, and the method for MDB is an asynchronous method, promptly all are asynchronous to calling of MDB.

Because client must be finished various operations to the Bean object by the method for calling Bean, but synchronization call is to use the current thread of carrying out, calling probably of client gets clogged, asynchronous call then is to monopolize a thread, not calling of client can get clogged, and client often need be finished various operations to Bean by the asynchronous method that calls Bean.Therefore, in order to reach the asynchronous call to session Bean or entity B ean method, prior art has adopted circuitous means, promptly realizes asynchronous call to session Bean or entity B ean method by MDB.

In the prior art, the supplier of Bean provides a specific MDB for session Bean or entity B ean, and specifies the sign Topic of this MDB in Java message server (JMS), and specifies the accessible JMS protocol of messages of this MDB type.Simultaneously, concern one to one between supplier's designated identification Topic, the MDB of Bean and the Bean three.

To be prior art carry out the synoptic diagram of asynchronous call to the method for session Bean or entity B ean to Fig. 1, and Fig. 2 is prior art is carried out asynchronous call to the method for session Bean or entity B ean a process flow diagram.Referring to Fig. 1 and Fig. 2, in the prior art, realize that the detailed process of the method for session Bean or entity B ean being carried out asynchronous call may further comprise the steps:

Step 201: client is in the context (Context) of JMS server, and finding (lookup) is the session Bean or the corresponding sign of the entity B ean Topic of client call with target Bean.

Step 202: client is sent to the JMS server with the JMS message of request call target Bean asynchronous method.

Here, the JMS protocol of messages type that sends of client is the supplier of a Bean specified JMS protocol of messages type when disposing this target Bean.And, carry the title of target Bean method in the JMS message that client sends.

Step 203:JMS server judges currently whether have other to be invoked at execution, if then execution in step 204, otherwise direct execution in step 205.

Step 204:JMS server is kept at calling of client and calls in the formation, when the poll next time of invokes thread arrives, returns step 203.

Step 205:JMS server sends to the JMS message that receives on the MDB corresponding with the sign Topic that finds.

Step 206:MDB resolves JMS message, finds target Bean in the context of EJB server, obtains the example of Bean then by the Home interface of this target Bean.

Here, because have corresponding relation between target Bean that client will be called and the MDB, so MDB finds the Bean corresponding with it in the context of EJB server after, promptly found target Bean.

Step 207:MDB sends message call to EJB framework (EJB Stub), and the interface parameters of carrying target Bean in this message call.

Step 208:EJB framework deposits the allocating object of being created in current calling in the formation for target Bean creates an allocating object.

Step 209:EJB framework judges currently whether have invokes thread to carry out on target Bean, if then execution in step 210, otherwise direct execution in step 211.

Step 210: wait for current calling in the formation, when the poll next time of invokes thread arrives, return step 209.

Step 211: current invokes thread obtains to carry out lock, and the EJB framework passes to Enterprise Java Bean container with current invokes thread.

Step 212:EJB container calls the method for the required target Bean of client.

Fig. 3 is prior art is carried out synchronization call to the method for session Bean or entity B ean a process flow diagram.Referring to Fig. 3, in the prior art, realize that the detailed process of the method for target session Bean or entity B ean being carried out synchronization call may further comprise the steps:

Step 301: it is client session Bean that will call or the Home interface of entity B ean that client finds (lookup) target Bean by the Home Stub of Bean in the client context.

Step 302: the create () method of the Home interface that client finds by calling is created a Bean example, and by the method for target Bean at the Remote of client Stub invocation target Bean.

Step 303:EJB framework is created a synchronization call object, and this synchronization call object is deposited in the current synchronizing thread that calls formation of SFSB object instance framework.

Step 304:EJB framework judges currently whether have invokes thread to carry out on target Bean, if then execution in step 305, otherwise direct execution in step 306.

Step 305:EJB framework is kept at calling in the formation described in the step 303 with calling of client, when the poll next time of invokes thread arrives, returns step 304.

Step 306: current synchronization call thread obtains to carry out lock, and the EJB framework takes out the synchronization call object and gives Enterprise Java Bean container.

Step 307:EJB container calls the method among the required target Bean of client.

This shows that there is following shortcoming in the process that existing techniques in realizing is called the method for session Bean or entity B ean:

1, the method for synchronous to EJB calls the different approach of having taked with asynchronous method, client can't state that it calls by unified means, thereby has increased the difficulty that client realizes calling the EJB method greatly.

2, must be to the asynchronous call of session Bean or entity B ean method through 6 layers of structure, promptly JMS client, JMS server, MDB, EJB framework, Enterprise Java Bean container and target Bean make invoked procedure numerous and diverse, greatly reduce system performance.

3, client is carried out asynchronous call to the method for session Bean or entity B ean, finish to MDB by sending JMS message, so the supplier of Bean it must be understood that the framework of JMS, so just can make its MDB that provides to parse JMS message, thereby for the Bean supplier has increased work difficulty, reduce Bean supplier's production efficiency, and reduced the maintainability of using.

4, the supplier of Bean needs the protocol type that the analysable JMS message of regulation MDB is deferred to, and this protocol type is not sought unity of standard, so it is different that the JMS protocol of messages type that causes Bean supplier regulation easily and the JMS protocol of messages type of client transmission exist, and can't carry out thereby cause calling.

Specified type of message protocol when 5, the JMS protocol of messages type that sends of the client supplier that is necessary for Bean disposes Bean, client must be able to be made the JMS message of different agreement type, therefore client is proposed higher requirement, increased the difficulty of client call.

6, in order to realize the asynchronous call to session Bean or entity B ean method, needs are bought the JMS server and it are managed and safeguards, thereby have increased the business development merchant's of Bean cost and workload greatly.

Summary of the invention

In view of this, fundamental purpose of the present invention is to provide a kind of method that the method for enterprise-level Java assembly is called, thereby simplifies the process of client call EJB method greatly.

In order to achieve the above object, technical scheme of the present invention is achieved in that

A kind of method that the method for enterprise-level Java assembly is called, designation method in the description document of the enterprise-level Java of appointment assembly EJB among the described EJB of statement is an asynchronous method, Enterprise Java Bean container is disposed the EJB of described appointment according to the statement in the described description document, and this method that method of enterprise-level Java assembly is called is further comprising the steps of:

A, the client application programming interfaces by EJB are sent to the EJB framework with the request of invocation target EJB method;

Whether B, EJB framework judge in the description document of target EJB that the method with the target EJB of client call is claimed as asynchronous method, if, execution in step C then, otherwise, the invoke synchronous method carried out, then process ends;

C, EJB framework are created an asynchronous call object, are asynchronous call thread that is not used of asynchronous method startup of target EJB, then this asynchronous call thread are passed to the container of target EJB;

Asynchronous method among D, this Enterprise Java Bean container invocation target EJB.

When described target EJB when state session Bean is arranged, the execution invoke synchronous method described in the step B may further comprise the steps:

B1, EJB framework create a synchronization call object, and deposit this synchronization call object in object instance framework calling in the formation, and whether judge then currently has other invokes thread to carry out on target EJB, if have, execution in step B2 then, otherwise, direct execution in step B3;

B2, EJB framework are blocked in calling of client in the thread, after other invokes thread of carrying out on the EJB at client call all is finished, and execution in step B3;

B3, EJB framework make the invokes thread of client obtain to carry out lock, then this invokes thread are passed to the container of target EJB;

The required method for synchronous of client among B4, this Enterprise Java Bean container invocation target EJB finishes the flow process of current invoke synchronous method then.

When described target EJB was stateless session Bean or entity B ean, the execution invoke synchronous method described in the step B may further comprise the steps:

B1, EJB framework are created a synchronization call object, and deposit this synchronization call object in object instance framework calling in the formation;

B2, EJB framework place the current thread of carrying out with calling of client on target EJB;

The required method for synchronous of client among B3, the target Enterprise Java Bean container invocation target EJB finishes the flow process of current invoke synchronous method then.

Among the step C, create between an asynchronous call object and asynchronous call thread that is not used of asynchronous method startup, further may further comprise the steps for target EJB at the EJB framework:

C1, EJB framework judge currently whether have other invokes thread to carry out on target EJB, if, execution in step C2 then, otherwise, continue to carry out the described step that starts an asynchronous call thread that is not used for the asynchronous method of target EJB;

C2, EJB framework are preserved calling of client, when the poll next time of invokes thread arrives, return step C1.

As seen, the method for the present invention's proposition has the following advantages:

1, the method for synchronous to EJB calls by identical approach with asynchronous method, and client can state that it calls by unified means, thereby simplifies the process of client call EJB method greatly.

2, the asynchronous method of EJB is called only need through 3-tier architecture, i.e. EJB framework, Enterprise Java Bean container and target Bean, thus simplified process greatly to EJB method asynchronous call, improved system performance.

3, in the present invention, the supplier of Bean need not to understand the framework of JMS, only needs the more bottom details of encapsulation in the Enterprise Java Bean container that it provides, thereby greatly reduces Bean supplier's work difficulty, and the maintainability of using is provided.

4, be the JAVA interface of standard between client and Enterprise Java Bean container, be application programming interfaces (API), client need not to construct JMS message when calling Bean, thereby guaranteed the correctness of message between the client and server, reduced the error probability of system.

When 5, client is carried out asynchronous method and called on Bean, needn't call the JMS message of structure specific protocol type, not need to understand that JMS uses, thereby simplified calling of client greatly for asynchronous method.

6, the asynchronous call on-line operation of client is on the interface of Bean, make that client invoked procedure synchronous to Bean and asynchronous method is identical, so the supplier of Bean can take unified means statement Bean synchronously and asynchronous method, thereby bring great convenience for the supplier of Bean.

Description of drawings

Fig. 1 is prior art is carried out asynchronous call to the method for session Bean or entity B ean a synoptic diagram.

Fig. 2 is prior art is carried out asynchronous call to the method for session Bean or entity B ean a process flow diagram.

Fig. 3 is prior art is carried out synchronization call to the method for session Bean or entity B ean a process flow diagram.

Fig. 4 is the present invention carries out asynchronous call to the method for session Bean or entity B ean a process flow diagram.

Fig. 5 does not have the process flow diagram that other calls SFSB container execution invoke synchronous method when carrying out in the present invention.

Fig. 6 has other to call the process flow diagram of SFSB container execution invoke synchronous method when carrying out in the present invention.

Embodiment

For making the purpose, technical solutions and advantages of the present invention clearer, the present invention is described in further detail below in conjunction with drawings and Examples.

In the present invention, the supplier of Bean customizes a description document for the session Bean or the entity B ean that call with asynchronous system of appointment, and states among the Bean by the title of the method for asynchronous call in this description document.Here, the session Bean that calls with asynchronous system of described appointment or entity B ean are according to the demand of operator and appointment by the supplier of Bean.At this Bean of Enterprise Java Bean container deploy, Enterprise Java Bean container then generates the Stub of EJB server stake (Stub) and user side respectively, has encapsulated the details of interacting message when calling Bean between the Stub of server end and user side.Stub with client is input in the client context then.

Fig. 4 is the present invention carries out asynchronous call to the method for session Bean or entity B ean a process flow diagram.Referring to Fig. 4, in the present invention, realize that the detailed process of the method for session Bean or entity B ean being carried out asynchronous call may further comprise the steps:

Step 401: it is client session Bean that will call or the Home interface of entity B ean that client finds (lookup) target Bean by the Home Stub of Bean in the client context.

Here, the Home interface that client finds is the JAVA interface of standard, i.e. API.And client knows that according to the interface definition that the supplier provided of Bean the method for being called is an asynchronous method.

Step 402: the create () method of the Home interface that client finds by calling is created a Bean example, and calls the method for Bean at the Remote of client Stub by target Bean.

Step 403:EJB framework judges whether the method for the target Bean of client call is designated as asynchronous method in the description document of target Bean, if then execution in step 404, otherwise, carry out the invoked procedure of method for synchronous, and jump out this flow process.

Step 404:EJB framework is created an asynchronous call object, deposits it in target Bean calling in the formation.

Step 405:EJB framework judges currently whether have invokes thread to carry out on target Bean, if then execution in step 406, otherwise direct execution in step 407.

Step 406:EJB framework is kept at calling in the formation described in the step 404 with calling of client, when the poll next time of invokes thread arrives, returns step 405.

Step 407:EJB framework is that the asynchronous invoking method of client starts a new asynchronous call thread, takes out above-mentioned asynchronous call object and gives the Enterprise Java Bean container execution, and this asynchronous call thread obtains to carry out lock.

Step 408:EJB container calls the asynchronous method of the required target Bean of client.

Because session Bean is divided into state session Bean (SFSB) and stateless session Bean (SLSB) are arranged, and SFSB requires to preserve order status, a plurality of calling must be carried out successively, and SLSB does not need preservation state, and a plurality of calling can be carried out simultaneously.Therefore, when the method for session Bean or entity B ean is called, the invention provides a preferable scheduling mechanism: will call layer and be divided into two types, a kind of is at the sequence call layer that state session Bean is arranged, and another kind is the concurrent invocation layer at stateless session Bean and entity B ean.

When client call had the method for state session Bean, Enterprise Java Bean container directly used the sequence call layer that this EJB method is called, and it calls the four kinds of situations that are divided into: other is invoked at current nothing when target Bean is last to be carried out, and the SFSB container is carried out asynchronous method and called; Current have other to be invoked at when target Bean is last to be carried out, and the SFSB container is carried out asynchronous method and called; Other is invoked at current nothing when target Bean is last to be carried out, and the SFSB container is carried out method for synchronous and called; Current have other to be invoked at when target Bean is last to be carried out, and the SFSB container is carried out method for synchronous and called.

No matter current whether have other be invoked at client required have state session Bean to go up to carry out, Enterprise Java Bean container uses the sequence call layer identical to there being state session Bean to carry out the detailed process that detailed process that asynchronous method calls and the invention described above realization carry out asynchronous call to the EJB method.

Fig. 5 does not have the process flow diagram that other calls SFSB container execution invoke synchronous method when carrying out in the present invention.Referring to Fig. 5, in the present invention, if current nothing other be invoked at client required have state session Bean go up to carry out the time, the SFSB container is realized the detailed process that has state session Bean method for synchronous to call be may further comprise the steps:

Step 501～step 502 and step 401～identical to step 402.

Step 503:EJB framework is created a synchronization call object, and this synchronization call object is deposited in the current synchronizing thread that calls formation of SFSB object instance framework.

Step 504: current synchronization call thread obtains to carry out lock, and the EJB framework takes out the synchronization call object and gives the Enterprise Java Bean container execution.

Step 505:EJB container calls the method for synchronous among the required target Bean of client.

Fig. 6 has other to call the process flow diagram of SFSB container execution invoke synchronous method when carrying out in the present invention.Referring to Fig. 6, in the present invention, if current have other to be invoked at required the having when carrying out on the state session Bean of client, the SFSB container realizes that the detailed process that the method for synchronous that state session Bean is arranged is called may further comprise the steps:

Step 601～step 603 is identical with step 501～step 503.

Step 604: have other invokes thread on Bean, to carry out owing to current,, wait wait order so this invokes thread gets clogged.

Step 605: invokes thread is notified, informs that the invokes thread of front has been finished execution.

Step 606: this invokes thread obtains to carry out lock, and the EJB framework passes to Enterprise Java Bean container with the synchronization call thread.

The required method for synchronous of client among the step 607:EJB container invocation target Bean.

When the method for client call stateless session Bean or entity B ean, Enterprise Java Bean container directly uses the concurrent invocation layer that this target EJB method is called, and its realization mechanism is:

If the asynchronous method of client call stateless session Bean or entity B ean, no matter current whether have other to be invoked at this Bean to go up and carry out, and the concurrent invocation layer is with the thread pool available in the system of being distributed to that calls of client, and execution is called.This invoked procedure is specially, and carries out in the above-mentioned detailed process of the EJB method being carried out asynchronous call the institute except that step 405 and step 406 in steps.

If the method for synchronous of client call stateless session Bean or entity B ean, no matter current whether have other to be invoked at this Bean to go up and carry out, and Enterprise Java Bean container uses the concurrent invocation layer directly to carry out calling of client in the thread that current execution is called.

In a word, the above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.

Claims

1, a kind of method that the method for enterprise-level Java assembly is called, it is characterized in that, designation method in the description document of the enterprise-level Java of appointment assembly EJB among the described EJB of statement is an asynchronous method, Enterprise Java Bean container is disposed the EJB of described appointment according to the statement in the described description document, and this method that method of enterprise-level Java assembly is called is further comprising the steps of:

A, client are sent to the EJB framework by application programming interfaces with the request of invocation target EJB method;

Whether B, EJB framework judge in the description document of target EJB that the method with the target EJB of client call is claimed as asynchronous method, if, execution in step C then, otherwise, invoke synchronous method, process ends then;

2, method according to claim 1 is characterized in that, when described target EJB when state session Bean is arranged, the execution invoke synchronous method described in the step B may further comprise the steps:

3, method according to claim 1 is characterized in that, when described target EJB was stateless session Bean or entity B ean, the execution invoke synchronous method described in the step B may further comprise the steps:

4, method according to claim 1 is characterized in that, among the step C, creates between an asynchronous call object and the asynchronous call thread that is not used of asynchronous method startup for target EJB at the EJB framework, further may further comprise the steps: