CN102508668A - AOP (Aspect Oriented Programming) implementation method of EJB 3 (Enterprise Java Beans 3) containers based on dynamic stack - Google Patents
AOP (Aspect Oriented Programming) implementation method of EJB 3 (Enterprise Java Beans 3) containers based on dynamic stack Download PDFInfo
- Publication number
- CN102508668A CN102508668A CN2011103577816A CN201110357781A CN102508668A CN 102508668 A CN102508668 A CN 102508668A CN 2011103577816 A CN2011103577816 A CN 2011103577816A CN 201110357781 A CN201110357781 A CN 201110357781A CN 102508668 A CN102508668 A CN 102508668A
- Authority
- CN
- China
- Prior art keywords
- blocker
- stack
- operational approach
- ejb
- dynamic
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 142
- 235000006719 Cassia obtusifolia Nutrition 0.000 title abstract 2
- 235000014552 Cassia tora Nutrition 0.000 title abstract 2
- 244000201986 Cassia tora Species 0.000 title abstract 2
- 238000013459 approach Methods 0.000 claims description 42
- 230000007246 mechanism Effects 0.000 claims description 6
- 230000011514 reflex Effects 0.000 claims description 4
- 230000000694 effects Effects 0.000 claims description 2
- 230000008569 process Effects 0.000 abstract description 6
- 238000012545 processing Methods 0.000 abstract description 5
- 230000004048 modification Effects 0.000 abstract description 4
- 238000012986 modification Methods 0.000 abstract description 4
- 230000007547 defect Effects 0.000 abstract 1
- 244000046052 Phaseolus vulgaris Species 0.000 description 12
- 235000010627 Phaseolus vulgaris Nutrition 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000002950 deficient Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000036651 mood Effects 0.000 description 3
- 230000003068 static effect Effects 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 239000003795 chemical substances by application Substances 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 206010003830 Automatism Diseases 0.000 description 1
- 244000131316 Panax pseudoginseng Species 0.000 description 1
- 235000005035 Panax pseudoginseng ssp. pseudoginseng Nutrition 0.000 description 1
- 235000003140 Panax quinquefolius Nutrition 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 235000008434 ginseng Nutrition 0.000 description 1
- 238000002347 injection Methods 0.000 description 1
- 239000007924 injection Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
Images
Abstract
An AOP (Aspect Oriented Programming) implementation method of EJB 3 (Enterprise Java Beans 3) containers based on dynamic stack achieves the business method interception of the EJB containers through the combination of pre-compilation and dynamic stack. According to the characteristic that system services such as log, transaction management and security process all EJB in the same way, corresponding codes are regenerated into source codes through pre-compilation, so as to reduce the time for processing the requests of interceptors; and intrusive modifications of the source codes are minimized through configuration files. As for the EJB business method interceptors, considering the characteristic that the interceptor classes are often modified and edited by programmers, the method adopts dynamic stack to avoid the defect that the source codes are repeatedly generated by pre-compilation; and compared with the dynamic proxy method, the method provided by the invention saves a great amount of memory space for generating dynamic proxy classes. The business method interception speed and flexibility of the EJB containers are improved through the static-dynamic combination.
Description
Technical field
The present invention proposes a kind of method of tackling under the Java EE system architecture based on the realization EJB3 operational approach of dynamic stack.This method combines mode difference disposal system rank and other blocker method of operational approach level of precompile and dynamic stack, has improved speed and the dirigibility of Enterprise Java Bean container to the operational approach interception.
Background technology
AOP is the abbreviation of Aspect Oriented Programming, promptly towards tangent plane programming.
The AOP techniques make use is a kind of to be called the technology of " crosscut ", and object that analysing the Kaifeng dress is inner, and those public behaviors that influenced a plurality of types are encapsulated into a reusable module; And with its by name " Aspect ", i.e. aspect is just with those and independent of service; But encapsulate for the logical OR responsibility that business module called jointly; Be convenient to reduce the duplicated code of system, reduce the degree of coupling of intermodule, and help following operability and maintainability.
" crosscut " technology of use, AOP is divided into two parts to software systems: core focus and crosscutting concerns.The main flow process of business processing is the core focus, concerns that with it little part is a crosscutting concerns.Characteristics of crosscutting concerns are that they often occur in the many places of core focus, and all similar basically everywhere.Such as purview certification, daily record, issued transaction.The purpose of AOP is exactly that the core focus is separated with crosscutting concerns.
EJB3.0 has introduced the blocker notion among the AOP, points out that the programmer can add other non-core services methods before and after the execution of operational approach be the blocker method.Blocker is the assembly that can tackle operational approach and the life cycle incident of bean, before these methods are visited, tackle then before or after add some operation.
But why in the EJB3 standard, introduce blocker? Can know that from the narration of front blocker is the part towards tangent plane programming; Tangent plane can be regarded focus as; Such as operations such as the affairs of being done before at the main business logic code of execution, safety; Though these operations are more common, also can run through whole procedure all the time, make to be flooded with a large amount of identical codes in the program code; Not only weaken the readability of code, and brought unnecessary trouble for the exploitation and the maintenance of application program.Had after the blocker; Just can tackle main service logic; Come into the code of non-service logic " injection ", realize separating of business logic codes and codes such as unessential relatively safety, daily record, improve the maintainable and readable of application program.
Realize the technology of AOP at present, mainly be divided into two big types: the one, adopt the dynamic proxy technology, utilize the mode of intercepts messages, the agent object that dynamically generates original object is to replace the execution of original object behavior; The 2nd, adopt the static mode that inweaves, introduces specific Grammer creation " aspect ", thus make compiler can compile duration inweave about " aspect " code.The main flow project that has realized AOP under the current Java platform mainly contains AspectJ, JBoss, Spring.
The representative of precompile mode is AspectJ.AspectJ has adopted the mode that in the precompile process, regenerates source code, own special compiler and AOP grammer arranged, but AspectJ does not utilize reflection technology or agent skill group, and only is the static state expansion of program.Though yet the AOP that this source code generating mode is realized possesses certain advantage on performance, it is too complicated, and the intrusive mood programming of revising source code has destroyed the structural of original code, brings certain problem to exploitation.
The AOP of JBoss and Spring realizes that the dynamic proxy that has utilized JDK to provide is technological.When intercepting the request of operational approach, the blocker metadata information according to the operational approach needs are carried out generates proxy class Proxy successively, and forms a chain structure, carries out these blocker methods successively.
Summary of the invention
The objective of the invention is to overcome the defective of precompile and dynamic proxy dual mode AOP realization; A kind of EJB3 container A OP implementation based on dynamic stack is provided, and the mode of using precompile and dynamic stack dual mode to combine realizes the interception of Enterprise Java Bean container to operational approach.To like system services such as daily record, transaction management and safety to the consistent characteristics of all EJB processing modes; Respective code is regenerated source code through the precompile mode; Reduced the time of handling the blocker request, and made the intrusive mood that as far as possible reduces source code revise through the mode of configuration file.For the operational approach blocker of EJB, consider that the programmer often revises the characteristics of editor's blocker class, adopts the mode of dynamic stack to avoid precompile to generate the defective of source code repeatedly; Compare the dynamic proxy mode simultaneously and practiced thrift the memory headroom of a large amount of generation dynamic proxy classes.Use static speed and dirigibility of operational approach being tackled with the raising Enterprise Java Bean container that dynamically combines.
For achieving the above object, the technical scheme that the present invention adopts is:
Different according to effect of blocker method and character are divided into two types of system level and service logic ranks with the blocker method, adopt the mode of precompile and dynamic stack to handle the corresponding blocker method of EJB3 respectively.
1) precompile mode disposal system rank blocker method:
Enterprise Java Bean container has separated some general utility functionss of general application system; For example performance optimizations such as affair mechanism, security mechanism and object pool or thread pool are machine-processed; These functions are nearly all needs of each application system, therefore can from concrete application system, separate.The blocker method of system level mainly just is meant the general utility functionss such as daily record, safety and transaction management to EJB; The blocker method of this type is transferred to Enterprise Java Bean container carries out, this to exploitation of simplifying EJB, safeguard the EJB operation stability and rapidity all very extremely important.
Through precompiler mode these class methods are inweaved in the source code, before the execution of operational approach, insert corresponding pre-service and can accomplish separating and interception of systemic-function method and service logic method with after-treatment system rank blocker method call with the execution back.
When the system level interception function that will manage when Enterprise Java Bean container was a lot, precompiler speed can corresponding reduction.Under the situation that system level interception function changes or modification is very big that Enterprise Java Bean container will be managed, precompiler template also will be made loaded down with trivial details modification, and this has brought inconvenience just for the precompile mode.
Therefore, the code that inweaves for precompile provides unified interface, and it is particularly important to simplify precompiler process.The precedence of the system level blocker function executing that provides according to Enterprise Java Bean container, utilize reflex mechanism with these methods stacked successively with pop, carry out the method that is positioned at stack top successively through the mode that plays stack, alleviated the pressure of safeguarding the compiling template greatly; Reduced modification simultaneously as far as possible, improved precompiler speed source code.
2) the dynamic stack mode logical level blocker method of managing business
The EJB3 standard is pointed out the programmer except can using system rank blocker, can also self-defined operational approach blocker and life cycle blocker, and these two kinds are referred to as " service logic blocker ".
Compare with the system level blocker method of the realization general utility functions of being managed by Enterprise Java Bean container, the service logic blocker of EJB is safeguarded by the programmer.The programmer often need revise editor's blocker class and method; If what employing precompile mode need not stopped inweaves different codes in the EJB source code; The consequence that causes is exactly the precompile cost that a very little change need cost a lot of money, and has increased the burden of exploitation.
If adopt the employed dynamic proxy mode of current most of application server,, formed dynamic proxy class chain according to the sequencing that calls for each service logic rank blocker class of EJB has all generated a dynamic proxy class.Though the dynamic proxy mode can avoid precompile to generate the shortcoming of source code repeatedly, and following defective is also arranged.The class that generates when the dynamic proxy class is operation consumes certain memory headroom; And the dynamic proxy class can not do any substantial work, and it can only intercept the call request of operational approach, and with calling the processing class of being given to a call request, and this type also must be that caller provides.
The mode of use dynamic stack has been avoided the two defective, neither need other blocker method of service logic level be inweaved in the source code through precompile also need not generate the dynamic proxy class and the processing that has realized call request class is provided as the dynamic proxy mode.
Intercept after operational approach calls, according to the self-defined blocker class relevant in the metadata of the EJB that resolves and the information of method, order as requested is stacked successively with the blocker method.The information of method stack and operational approach is packaged into one calls the blocker method that context InvocationContext passes to first execution.Each blocker method body all is divided into three parts: at first being the pre-service code before operational approach is carried out, secondly is the aftertreatment code after operational approach is carried out, and between pre-service and post-processed, carries out follow-up blocker method.The concrete step of carrying out follow-up blocker method is: eject stack top blocker method, and the information that will eject stack and the operational approach of stack top blocker method is packaged into InvocationContext again and passes to this method, call this method through reflex mechanism at last.After follow-up blocker method was carried out and returned, this blocker method can continue to have carried out follow-up aftertreatment work.
Description of drawings
Fig. 1 is the interface synoptic diagram of precompile source file.
Fig. 2 resolves EJB blocker metadata and with stack inner structure synoptic diagram behind its pop down.
Fig. 3 is the stack inner structure synoptic diagram of certain operational approach of supposition.
Fig. 4 is combine with dynamic stack cooperation executive system rank and a service logic rank blocker method sequential chart of precompile under the situation of Fig. 2.
Embodiment
Below in conjunction with accompanying drawing the present invention is described further.
1) precompile mode disposal system rank blocker method
EJB divides from type, can be divided into stateless session bean, state session bean is arranged, entity bean and message-driven bean; Can also be divided into BMT (bean management practices) and CMT (Container Management affairs) from the affairs management type; The combination of every kind of different classification all has own specific pretreatment mode; Can pass through to be the different different precompile base class of classification customization, thereby and let these precompiler base class realize that all the precompile interface reaches the simplification of in the simplification preprocessing process source code being revised and perhaps do not revise source code as far as possible.
Precompile is not in fact revised source file and has been destroyed the structural of original code to prevent the intrusive mood programming of revising source code.On the contrary, the interface inherited according to the source file class of precompile has generated file after the new compiling.The object of this compiling back document creation source file class after intercepting call request, activates the corresponding method of object.
Like Fig. 1 is the interface of precompile source file, can see that all base class of having realized the precompile interface all need realize executePreSysInterceptor (carry out operational approach call before system level blocker method), executeMethod (execution operational approach), executePostSysInterceptor (carrying out the system level blocker method after operational approach is called).After the precompile in the file method structure be:
The parent that at first is such that is to say the PreSysInterceptor method in the precompile base class; Next is the method name and the parameter of the current method of encapsulation, and they are passed to the executeMethod method of parent as parameter; Its parent that is to say the PostSysInterceptor method in the precompile base class at last.
Therefrom can see the execution sequence of these three methods in each method body, the source file after the compiling is not revised the actual code of carrying out yet.It hands to precompiler base class with request, and realizes the pre-process and post-process of system level blocker method to run time version by this base class.
The step of system level blocker method was following before and after the execution operational approach was called:
1, the systemic-function of the various different classes of required uses of EJB of configuration in configuration file.
Read these configuration informations when 2, Enterprise Java Bean container starts.
When 3, client is searched EJB according to JNDI, return the object of corresponding compiling back file.
When 4, calling operational approach, the pre-service in the system level blocker method is pressed in the stack successively according to configuration information.
5, each blocker method that is positioned at stack top that ejects is carried out it, ejects the stack top method again after finishing, and is empty until stack.
6, call corresponding operational approach in the source file class object, preserve execution result.
7, according to configuration information the aftertreatment in the system level blocker method is pressed in the stack successively, adopts and the execution of preprocess method same procedure.
8, execution result is returned to client.
2) the dynamic stack mode logical level blocker method of managing business
The EJB3 standard can be divided into the blocker class of EJB following four kinds according to reach: default blocker class, and automatism is in all service logic method and life cycle methodologies of all EJB; Type level blocker class acts on all service logic method and life cycle methodologies of the EJB of appointment; Method level blocker class only acts on the specific transactions method of certain specified EJB, the life cycle incident that can not be used to tackle bean; Bean level blocker class, the self-blocker that is otherwise known as can only act on this EJB itself.
A lot of blocker classes all can be arranged on each operational approach of bean and the life cycle methodology; Each blocker class all has and only has a blocker method; It can call these blocker methods in a certain order when interception takes place, and finally carries out the business or the life cycle methodology of appointment.
The execution sequence of blocker method receives the constraint of the priority and the inheritance of blocker class.In general, be defined in the blocker that priority ratio that the blocker of outer category carries out is defined in the Bean class and want high; The priority of default blocker class is greater than the priority of class level blocker class, and the priority of type level blocker class is greater than the priority of method level blocker class, and the priority of method level blocker class is again greater than the priority of bean level blocker class; The priority of parent blocker is greater than the priority of subclass blocker class; The parent of bean level blocker class is the priority of the priority of EJB parent blocker method greater than the blocker method that defines among the EJB; The blocker method of the blocker class of same level is carried out according to the order of definition in configuration file or the mark.
As shown in Figure 2 is with the structural representation behind each blocker pop down.Pop down and to carry out the algorithm of blocker method and operational approach afterwards as follows: (stack S1 is set is used to store the order of calling the blocker class)
1, according to the execution sequence of blocker class; The blocker class of carrying out the blocker method at last is pressed into stack S1; Be that the last blocker class of carrying out the blocker method in the remaining blocker class is pressed into stack S1 successively, then the stack top of stack S1 is the highest blocker class of priority.
InvocationContext instances of composition of content such as the real ginseng of 2, importing into according to method name, the EJB class name of define method, the method for operational approach, method return type are made as ctx.
3, judge whether S1 is empty, if, then carry out the service logic method, change 4; Otherwise eject stack top blocker class and be made as P; Call the blocker method of P and ctx is passed to the blocker method as parameter; In the blocker method implementation of P, can implement this step of ctx.proceed (), in the inner execution 3 of Invocation.proceed () method.
4, the blocker method is returned from level to level, is finished until the blocker method of the highest blocker class of priority.
Fig. 3 is the stack inner structure of certain operational approach of supposition; Fig. 4 is combine with dynamic stack cooperation executive system rank and a service logic rank blocker method sequential chart of precompile under the situation of Fig. 2, can see that therefrom the whole service method call cuts the implementation of device method.
Claims (2)
1. EJB3 container A OP implementation method based on dynamic stack; It is characterized in that: different according to effect of blocker method and character; The blocker method is divided into two types of system level blocker method and service logic rank blocker methods, adopts the mode of precompile and dynamic stack to handle the corresponding blocker method of EJB3 respectively;
1) precompile mode disposal system rank blocker method:
Before the execution of operational approach with after carrying out, insert corresponding pre-service and after-treatment system rank blocker method call step, accomplish separating and interception of systemic-function method and service logic method;
To above-mentioned invocation step the unified data interface is provided; Mode through configuration file indicates systemic-function method and the call sequence thereof that needs use; The precedence of the system level blocker function executing that provides in conjunction with the EJB3 container; Utilize reflex mechanism with these methods stacked successively with pop, carry out the method that is positioned at stack top successively through the mode that plays stack;
2) the dynamic stack mode logical level blocker method of managing business:
Intercept after operational approach calls, according to the self-defined blocker class relevant in the metadata of the EJB that resolves and the information of method, order as requested is stacked successively with service logic rank blocker method; During execution, at first eject the blocker method of stack top element, the information of method stack and operational approach is packaged into one calls the service logic rank blocker method that context InvocationContext passes to first execution;
Each service logic rank blocker method body all was divided into for three steps: at first be the pre-service before operational approach is carried out; Next is to carry out follow-up service logic rank blocker method or operational approach; Be the aftertreatment after operational approach is carried out at last;
Carry out after the follow-up blocker method, current blocker method continues to carry out aftertreatment work; Will in JVM, form a dynamic stack of calling the blocker method like this; This stack can constantly add the new blocker method of calling before the final execution of operational approach; And after operational approach is finished, constantly call the blocker method and return, in turning back to step 1), intercept the place of operational approach call request.
2. method according to claim 1; It is characterized in that: specifically carrying out the follow-up service logic rank blocker method or the step of operational approach is: if judge that from above-mentioned InvocationContext obtaining stack is not sky; Then eject stack top blocker method as the blocker method that next will carry out; And the information that will eject stack and the operational approach of stack top blocker method is packaged into InvocationContext again and passes to next blocker method, calls next blocker method through reflex mechanism at last; Otherwise stack is empty, obtains operational approach from InvocationContext, carries out this operational approach then.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110357781.6A CN102508668B (en) | 2011-11-11 | 2011-11-11 | AOP (Aspect Oriented Programming) implementation method of EJB 3 (Enterprise Java Beans 3) containers based on dynamic stack |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110357781.6A CN102508668B (en) | 2011-11-11 | 2011-11-11 | AOP (Aspect Oriented Programming) implementation method of EJB 3 (Enterprise Java Beans 3) containers based on dynamic stack |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102508668A true CN102508668A (en) | 2012-06-20 |
| CN102508668B CN102508668B (en) | 2014-11-05 |
Family
ID=46220760
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110357781.6A Active CN102508668B (en) | 2011-11-11 | 2011-11-11 | AOP (Aspect Oriented Programming) implementation method of EJB 3 (Enterprise Java Beans 3) containers based on dynamic stack |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102508668B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103793232A (en) * | 2014-02-20 | 2014-05-14 | 浪潮集团山东通用软件有限公司 | Component calling and extending frame implementation method based on AOP |
| CN103838564B (en) * | 2012-11-27 | 2017-02-15 | 重庆新媒农信科技有限公司 | Attribute loading method and system |
| CN106649061A (en) * | 2015-11-04 | 2017-05-10 | 阿里巴巴集团控股有限公司 | Method and device for recording user's operation log in web system |
| CN108196833A (en) * | 2018-01-09 | 2018-06-22 | 武汉斗鱼网络科技有限公司 | Implementation method, storage medium, electronic equipment and the system of AOP agent frameworks |
| CN108304195A (en) * | 2017-09-08 | 2018-07-20 | 武汉斗鱼网络科技有限公司 | A kind of implementation method, device and the electronic equipment of AOP components |
| CN108304184A (en) * | 2016-08-09 | 2018-07-20 | 上海思立微电子科技有限公司 | Compilation Method and device |
| CN109947415A (en) * | 2019-02-28 | 2019-06-28 | 东软集团股份有限公司 | Configuration method, device, storage medium and the electronic equipment of blocker |
| CN113448679A (en) * | 2020-03-25 | 2021-09-28 | 北京沃东天骏信息技术有限公司 | Method and device for processing call request |
| CN115996246A (en) * | 2023-03-23 | 2023-04-21 | 云粒智慧科技有限公司 | Processing method and device of target protocol request, electronic equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050222931A1 (en) * | 2003-08-27 | 2005-10-06 | Ascential Software Corporation | Real time data integration services for financial information data integration |
| CN101364185A (en) * | 2008-09-02 | 2009-02-11 | 中国科学院软件研究所 | Thread pool size self-adapting regulating method and concurrency control method applying server |
| CN102221998A (en) * | 2011-06-07 | 2011-10-19 | 北京大学 | Method for extending EJB container in component running support platform |
-
2011
- 2011-11-11 CN CN201110357781.6A patent/CN102508668B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050222931A1 (en) * | 2003-08-27 | 2005-10-06 | Ascential Software Corporation | Real time data integration services for financial information data integration |
| CN101364185A (en) * | 2008-09-02 | 2009-02-11 | 中国科学院软件研究所 | Thread pool size self-adapting regulating method and concurrency control method applying server |
| CN102221998A (en) * | 2011-06-07 | 2011-10-19 | 北京大学 | Method for extending EJB container in component running support platform |
Non-Patent Citations (1)
| Title |
|---|
| 武蕾娜等: "基于AOP的EJB访问控制功能的实现", 《计算机应用与软件》 * |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103838564B (en) * | 2012-11-27 | 2017-02-15 | 重庆新媒农信科技有限公司 | Attribute loading method and system |
| CN103793232A (en) * | 2014-02-20 | 2014-05-14 | 浪潮集团山东通用软件有限公司 | Component calling and extending frame implementation method based on AOP |
| CN106649061A (en) * | 2015-11-04 | 2017-05-10 | 阿里巴巴集团控股有限公司 | Method and device for recording user's operation log in web system |
| CN106649061B (en) * | 2015-11-04 | 2019-12-10 | 阿里巴巴集团控股有限公司 | Method and equipment for recording operation log of user in web system |
| CN108304184B (en) * | 2016-08-09 | 2021-04-23 | 上海思立微电子科技有限公司 | Compiling method and device |
| CN108304184A (en) * | 2016-08-09 | 2018-07-20 | 上海思立微电子科技有限公司 | Compilation Method and device |
| CN108304195A (en) * | 2017-09-08 | 2018-07-20 | 武汉斗鱼网络科技有限公司 | A kind of implementation method, device and the electronic equipment of AOP components |
| CN108304195B (en) * | 2017-09-08 | 2021-04-27 | 武汉斗鱼网络科技有限公司 | AOP assembly realization method and device and electronic equipment |
| CN108196833A (en) * | 2018-01-09 | 2018-06-22 | 武汉斗鱼网络科技有限公司 | Implementation method, storage medium, electronic equipment and the system of AOP agent frameworks |
| CN108196833B (en) * | 2018-01-09 | 2021-02-02 | 武汉斗鱼网络科技有限公司 | AOP proxy framework implementation method, storage medium, electronic device and system |
| CN109947415A (en) * | 2019-02-28 | 2019-06-28 | 东软集团股份有限公司 | Configuration method, device, storage medium and the electronic equipment of blocker |
| CN113448679A (en) * | 2020-03-25 | 2021-09-28 | 北京沃东天骏信息技术有限公司 | Method and device for processing call request |
| CN115996246A (en) * | 2023-03-23 | 2023-04-21 | 云粒智慧科技有限公司 | Processing method and device of target protocol request, electronic equipment and storage medium |
| CN115996246B (en) * | 2023-03-23 | 2023-06-09 | 云粒智慧科技有限公司 | Processing method and device of target protocol request, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102508668B (en) | 2014-11-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102508668B (en) | AOP (Aspect Oriented Programming) implementation method of EJB 3 (Enterprise Java Beans 3) containers based on dynamic stack | |
| US8769485B2 (en) | Data parallelism and parallel operations in stream processing | |
| US20080134158A1 (en) | Stream processor with compiled programs | |
| US7694272B2 (en) | Method, a language and a system for the definition and implementation of software solutions by using a visualizable computer executable modeling language | |
| US7836428B2 (en) | Declarative computer programming language method and system | |
| US6182277B1 (en) | Methods and apparatus for declarative programming techniques in an object oriented environment | |
| US8051405B2 (en) | System and method for build script generation in a software development environment | |
| US7546606B2 (en) | System and method using a connector architecture for application integration | |
| JP4514105B2 (en) | Extended runtime hosting | |
| CN113872948A (en) | Method for executing intelligent contract, block chain node and node equipment | |
| US7506315B1 (en) | System and method combining application tracing and distributed statistical records | |
| US20070089090A1 (en) | Method and system for protecting source code | |
| CN101937336B (en) | Software asset bundling and consumption method and system | |
| CN106844153B (en) | Application program operation monitoring method and device and terminal | |
| Conrad et al. | Temporal OCL: Meeting specification demands for business components | |
| WO2018032653A1 (en) | Function implementing method and apparatus for java card application | |
| US20060085400A1 (en) | Data access layer design and code generation | |
| US7743367B1 (en) | Registration method for supporting bytecode modification | |
| Kamburjan et al. | Behavioral contracts for cooperative scheduling | |
| CN115878097B (en) | Method and system for creating timing task | |
| CN101894317B (en) | System and method for driving business logic through data changes | |
| CN113553068B (en) | Method and device for downloading application package and electronic equipment | |
| Jarir et al. | Dynamic adaptability of services in enterprise JavaBeans architecture | |
| CN105393216B (en) | Run-time memory is adjusted | |
| Jézéquel | Reifying variants in configuration management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240403 Address after: 101, Section B, 1st Floor, No. 203, Zhongyuan 2nd District, Wangjing Lize, Chaoyang District, Beijing, 100102 Patentee after: Beijing Cool Data Technology Co.,Ltd. Country or region after: China Address before: 710049 No. 28 West Xianning Road, Shaanxi, Xi'an Patentee before: XI'AN JIAOTONG University Country or region before: China |