CN102221998A - Method for extending EJB container in component running support platform - Google Patents
Method for extending EJB container in component running support platform Download PDFInfo
- Publication number
- CN102221998A CN102221998A CN2011101510671A CN201110151067A CN102221998A CN 102221998 A CN102221998 A CN 102221998A CN 2011101510671 A CN2011101510671 A CN 2011101510671A CN 201110151067 A CN201110151067 A CN 201110151067A CN 102221998 A CN102221998 A CN 102221998A
- Authority
- CN
- China
- Prior art keywords
- metadata
- enterprise java
- ejb
- interceptor
- java bean
- 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.)
- Pending
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention relates to a method for extending an Enterprise JavaBean (EJB) container in a component running support platform. The method comprises the following steps of: firstly, generating a treelike metadata model, wherein the root node of the treelike metadata model is a metadata base class containing EJB base attributes, while the child nodes of the treelike metadata model are metadata containing new semantics, and the metadata of the child nodes inherits and extends the base class; next, analyzing the metadata and annotations thereof; obtaining, by the EJB container, class information requested in the running of the EJB by reading a configuration file, and loading the class information to complete the deployment of the EJB; and supporting the implementation of a specific service logic in the EJB container through an interceptor module so that the EJB container obtains resources defined by the metadata and the annotations thereof, thus realizing the extension of the EJB container. The method in the invention realizes an EJB container behaviour extension mechanism in a uniform metadata model driven architecture; the idea of software reuse is thoroughly embodied; and the costs of development, testing, maintenance and upgrading can be reduced.
Description
Affiliated technical field
The invention belongs to software technology field, relate to a kind of method by Enterprise Java Bean container in the extension member operation support platform under the unified metadata schema driving framework.
Background technology
The JavaEE platform is one of at present ripe, component operation support platform of being most widely used, and it provides solution based on member for exploitation based on the enterprise-level Distributed Application of Java language.It is incorporated into component technology in the distributed system on the one hand, has promoted the distributed software development technology based on member; On the other hand, people recognize and exist many public characteristics in most of distributed systems, for example affairs, safety or the like, by being peeled off out, these characteristics form public service, be integrated in the operation platform, for member provides good exploitation and running environment, make that the exploitation of distributed element system is more simple and efficient.
In the JavaEE notion, that important component part is EJB (Enterprise JavaBean) the most.The EJB emphasis is handled the service logic of JavaEE.The EJB member is arranged in the Enterprise Java Bean container of application server, and Enterprise Java Bean container can be in charge of the structure of these EJB members, and the complete environment time of running is destroyed and provided in scheduling.It is telescopic, businesslike using EJB framework written application program, and is multi-user's safety.
Along with the demand of user's application server constantly increases, we need realize the expansion of Enterprise Java Bean container semanteme and behavior with a kind of simple and easy reasonable manner, make Enterprise Java Bean container (for example comprise more function and characteristic, support group system, concurrency programming etc.), and don't need to change its original frame system, to reduce upgrade cost.
Summary of the invention
The method that the purpose of this invention is to provide Enterprise Java Bean container in a kind of extension member operation support platform, do not need to change its original frame system, instruct the application server developer to design a simple regular metadata schema, semantic only need of the expansion of definition Enterprise Java Bean container just can be realized by several steps simply fast.
The method of Enterprise Java Bean container in the extension member operation support platform of the present invention, its step comprises:
1, generate a tree-like metadata schema, its root node is the metadata base class that comprises the EJB base attribute, will comprise the child node of the metadata of neology as this metadata schema tree, and wherein the metadata of child node is inherited and expanded above-mentioned base class;
2, above-mentioned metadata and note thereof are resolved;
3, Enterprise Java Bean container obtains the required category information in service at EJB by reading configuration file, and it is loaded, and finishes the deployment of EJB;
4, support the realization of specific transactions logic in the Enterprise Java Bean container by interceptor module, Enterprise Java Bean container obtains above-mentioned metadata and the defined resource of note thereof, realizes the expansion of Enterprise Java Bean container.
The present invention supports the AOP in the Enterprise Java Bean container to call by the interceptor method of life cycle readjustment and the interceptor method of business procedure.
The present invention obtains interceptor chain in the Bean example by Enterprise Java Bean container; Create the interceptor chain of Bean type by the interceptor structure of Bean type; Create the interceptor chain of Bean example by the interceptor structure of Bean example; Call each method in the interceptor chain successively, realize the interceptor mechanism in the Enterprise Java Bean container.
The present invention injects Enterprise Java Bean container by relying on the mode of injecting with the resource of above-mentioned metadata and note definition thereof.By field injection and setter injection the resource of above-mentioned metadata and note definition thereof is injected Enterprise Java Bean container.
Enterprise Java Bean container of the present invention injects described resource before the interceptor method that any operational approach or the life cycle of EJB example are adjusted back is called.
The present invention will rely on to inject by described interceptor module and realize as a POJO, then this POJO be placed the top of interceptor chain of the PostConstruct type life cycle of each Enterprise Java Bean container as the interceptor of a system level.
The metadata of described child node is inherited the metadata base class of above-mentioned EJB directly or indirectly.
Resolver of the present invention adopts hierarchical structure, ground floor includes attitude session Bean, no attitude session Bean and message-driven Bean resolver, the second layer comprises that class is explained, method is explained and resolver is explained in the territory, the 3rd layer of resolver that comprises certain concrete note, resolver manages by its manager.
Method of the present invention comprises following three partial contents: the unified metadata schema of (1) design, support expansion behavior definition metadata and resolver; (2) by the operating process in the unified interceptor framework realization behavior expansion; (3) inject the resource acquisition that the mechanism optimization behavior is expanded by unified dependence.
According to the content of JavaEE standard, the realization of Enterprise Java Bean container semanteme relates generally to the deployment of two process: EJB and calling of EJB.The deployment of EJB mainly is the contract according to container and EJB, obtains the required context of EJB operation.Its flow process is:
● analytical element data and note (Annotation)
● read configuration file
● class loads
EJB calls the implementation procedure that has embodied the Enterprise Java Bean container semanteme, and its detailed process as shown in Figure 1.At first obtain business interface by Terminal Server Client or local client, by the method for these interface interchange encapsulation classes, with the encapsulation class of this process container generation.Call latter two time point that reaches before the service logic method of EJB in the encapsulation class, some services (as life cycle management, transaction management, persistence service, security service etc.) that may need to use Enterprise Java Bean container are to realize specific service logic.Thereby before operation EJB and calling interface to container service all is provided afterwards.
The behavior expansion of Enterprise Java Bean container is relevant with call flow with the deployment of EJB.Common mode is directly to revise or use another set of deployment and call flow, will make expansion process become complicated but do like this, and is unfavorable for the secondary expansion of container behavior.In order to address this problem, EJB is disposed in the present invention and the call flow unification makes up based on metadata schema.
Metadata schema is used for unifying the metadata source of bottom when disposing EJB, upwards provide an information interface that unanimity is complete to container, is convenient to the realization of analytical element data and annotation procedure.In our designed metadata schema, it at first is a data structure (BeanMetadataInfo), its content has comprised the fundamental that EJB is required, and as transaction attributes, security attribute, persistence attribute, interceptor chain etc., this data structure will be as the base class in the model.In order to make the behavior of expansion can unify to handle under regular metadata frame, the metadata category of expansion behavior need be inherited above-mentioned base class directly or indirectly.In addition, according to the needs of neology, also may exist between the metadata of expansion and inherit or incidence relation.Thereby metadata schema can be designed to the tree structure of a multilayer, as shown in Figure 2, base class BeanMetadataInfo is the root node of tree, and the metadata (a series of eXMetaInfo_ classes among Fig. 2) of expansion is directly inherited or indirect succession this base class, thereby as child node.Like this, when behavior is expanded, only need define metadata simply as shown in Figure 2, and get final product at this metadata schema tree interpolation respective leaves child node.
When disposing EJB, at first to resolve metadata and note.Note is some data that do not belong to program, is used for Enterprise Java Bean container and realizes specific function.The flow process of resolving is: 1. read in the source program with the initial statement of symbol ' @ '; 2. the property value with this statement is recorded in the container context; 3. obtain floor processor; 4. this metadata or note are handled.The present invention is by dynamic binding and search mechanism, bottom metadata processor Interface design two parts to realize resolving.Dynamic binding and the mechanism of searching have defined the mode that bottom annotation process device and metadata processor make up, and how to find suitable bottom annotation process device fast according to annotation object and finish processing procedure.
Bottom metadata processor interface definition metadata processor how all metadata notes types to be resolved required parameter transmission by a unified interface.Similar with the hierarchical structure of metadata schema, processor also adopts hierarchical structure, handles dissimilar notes respectively.
In the parsing to metadata and note, Enterprise Java Bean container obtains needed category information in the EJB operational process by reading configuration file, and it is loaded, to finish the deployment of EJB.
In 6 steps shown in Figure 1, the expansion of Enterprise Java Bean container behavior is mainly reflected in the the 2nd, the 3rd and the 5th link, and other link is a basically identical for different behaviors.To analyze this three step, serve and other element in order in the service logic of EJB, adding, but lead-in surface to be to the thought of tangent plane programming (AOP), for Enterprise Java Bean container designs unified interceptor framework.It need handle two parts: the interceptor method of life cycle readjustment (Lifecycle Callback) and the interceptor method of business (Business) process.The purpose difference of these two parts.For an EJB, the purpose of the interceptor method of its life cycle readjustment is to give the particular point in time of EJB in life cycle (as the PostConstruct that defines in EJB 3.0 standards, PrePassivate, PostActivate, PreDestroy) chance of the desired action of seeing of execution user---for example write daily record, access data or the like.The purpose of the interceptor method of operational approach then is to carry out adjunctive behavior (AroundInvoke that defines in such interceptor class such as EJB 3.0 standards) with a kind of uniform way.
The identical point of these two parts is that the method that they depend on user-defined interceptor carries out call operation, and their using method also is almost consistent simultaneously.Simultaneously, owing to (operational approach or life cycle) on the application point can have a plurality of interceptor methods to act on simultaneously, they all require the notion of an interceptor chain.
Therefore, two kinds of interceptor methods can be integrated, as shown in Figure 3: the 1.EJB container obtains the interceptor chain in the Bean example; 2. create the interceptor chain of Bean type by the interceptor structure of Bean type; 3. create the interceptor chain of Bean example by the interceptor structure of Bean example; 4. call each method in the interceptor chain successively, these methods have all realized InvocationContext interface (call context interface, be used for being kept at call the method and the attribute that use).Can simplify the upper strata framework of Enterprise Java Bean container semantic extension like this, and simplify the specific implementation of each interceptor method in the expansion semanteme.
Relying on injection is the defined mechanism of EJB 3.0 standards, and its maximum effect is to simplify user's calling logic, makes the user to carry out loaded down with trivial details search operation again and just can take needed object.The present invention uses to rely on and injects, with obtaining of the resource that defined in optimization metadata and the note.
Handle well to rely on and inject, mainly contain two problems: injection mode and injection timing.Relying on to inject generally has dual mode: field to inject and the setter injection.Field injects a territory that allows to class and injects resource, and setter allows to inject resource by calling the setter method.Use field to inject, only need territory of definition, then the resource that it is quoted with the Annotation mark or the equivalent form of value that adopts deployment descriptor.If resource name and the type quoted of definition, container will be inferred information from the title of field and type.And the setter injection allows the user by a setXxx of JavaBean normalized definition () method, and the resource that it is quoted with the Annotation mark or the equivalent form of value that adopts deployment descriptor.Application program needn't go to call this setter method, and container can call this setter method that is used to inject resource before calling operational approach.From the above, to these two kinds of injection modes, application server thing to be processed is similar.All be to find the object reference that needs injection with JNDI earlier, inject directly for filed then and give the territory, inject, get final product quoting as parameter call setter method for setter quoting to compose.
For injection timing, Enterprise Java Bean container injects this resource before need being called in the interceptor method that any operational approach or the life cycle of this EJB example are adjusted back.Therefore can will rely on by the interceptor module of front to inject and realize, then this POJO be placed the top of interceptor chain of PostConstruct type (i.e. triggering at once after the EJB makes up) life cycle of each EJB as the interceptor of a system level as a POJO (common java class).
Like this, just, realized the resource acquisition of expansion behavior in the Enterprise Java Bean container.
So far, the present invention has realized the Enterprise Java Bean container behavior extension mechanism under unified metadata schema driving framework.Utilize the metadata schema driving mechanism, Enterprise Java Bean container can fully keep and multiplexing basic framework when disposing and calling, definition for new behavior only need increase metadata and corresponding resolving simply, and inject mechanism by the interceptor and the dependence on unified upper strata, the processing framework that new behavior is realized all is consistent, this has demonstrated fully the thought of software repeated usage, can reduce the cost of exploitation, test, maintenance and upgrading.
Description of drawings
The invocation step synoptic diagram of Fig. 1 EJB
Fig. 2 metadata schema structural representation of the present invention
The call flow chart of Fig. 3 interceptor module
The metadata schema structural representation of EJB 3.0 semantemes of Fig. 4 specific embodiment of the invention
The EJB3.0 metadata parser class figure of Fig. 5 specific embodiment of the invention
The interceptor of Fig. 6 specific embodiment of the invention (AOP) module class figure
Embodiment
Below provide one and building an embodiment that drives the Enterprise Java Bean container behavior extension mechanism of realizing under the framework at unified metadata schema on the application server PKUAS.
PKUAS is the JavaEE application server by the independent development of software study institute of information science technology institute of Peking University, is a platform architecture based on micro-kernel, height componentization.Semanteme with definition EJB 3.0 is an example below, and implementation process of the present invention is described.
When the metadata schema of design EJB 3.0 semantemes, a base class BeanMetaInfo is arranged, its attribute comprises and relates to relevant attribute such as affairs, interceptor chain, safety, persistence, as the variable transactionType of record transaction types, and the interceptors chained list of record interceptor chain.The metadata SessionBeanMetaInfo of Session EJB has increased quoting two types of local sessions, remote session on the basis that has obtained the above-mentioned attribute of BeanMetaInfo.And stateless Session EJB and metadata that state session EJB arranged be respectively on the basis of having inherited the SessionBeanMetaInfo attribute, expanded separately to be used to write down their chained lists of required method in use.In addition, the metadata of message-driven EJB has been expanded own required attribute on the basis of having inherited the BeanMetaInfo attribute, as is used for the attribute linked-list of configuration messages.The meta-model structure of EJB3.0 semanteme as shown in Figure 4.
And handle for the basic note of EJB, defined resolver framework as shown in Figure 5:
ParserManager is the manager of resolver among Fig. 5, resolver adopts hierarchical structure, ground floor divides for attitude session Bean (SFBParser), no attitude session Bean (SLBParser) and message-driven Bean (MDBParser) resolver are arranged according to the type of EJB, the second layer is to explain (ClassParser) according to the type branch of explaining for class, method explains (MethodParser) and (Field) resolver is explained in the territory, the 3rd layer is exactly the resolver of concrete certain note, as ResourceParser, be used for Xie Xi @Resource specially.
For interceptor module, PKUAS adopts design shown in Figure 6.
The context class InvocationContextImpl that calls among Fig. 6 has realized the InvocationContext interface, comprises basic EJB context class BaseEJBContext in its attribute, and Bean example interceptor class BeanInstanceInterceptor.And in the BaseEJBContext class, comprise the base class BaseBeanMetaData of Bean metadata.The interceptor interface BeanTypeInterceptor that comprises the Bean type in the BaseBeanMetaData class.The BeanTypeInterceptor interface is the intercepting chain type of each EJB type of record, and BeanTypeInterceptorImpl is its realization.BeanInstanceInterceptor writes down the execution customizing messages constantly of certain intercepting chain of each example.InterceptorMeta is the interface of the metamessage of Interceptor, and InterceptorMetaImpl is its realization.Wherein BeanTypeInterceptorImpl and InterceptorMeta can be provided by deployment module, and BeanInstanceInterceptor can be generated by the EJB basic module in the time of running.Why wherein all having adopted Interface design is in order to reduce coupling, to strengthen the independence between the module, being convenient to the further renewal and the evolution of system.
And rely on the realization of injecting, and in PKUAS, set up a common java class DependencyInjectionPOJO, it has a method injectValues, has been put on the Annotation of PostConstruct.Can be in this method according to several injection types of rely on injecting: EJB, Resource, PersistenceContext and PersistenceUnit, and two kinds of injection mode: field inject and the setter injection, operate accordingly, finish injection.Can when being established, each EJB that expands behavior be packaged into InterceptorMeta is injected into its interceptor chain as the interceptor of system level top to this POJO then.Can make application program before other operation beginning, just finish the resource of obtaining expansion EJB like this, so far, realize expansion the Enterprise Java Bean container behavior.
Claims (9)
1. the method for Enterprise Java Bean container in the extension member operation support platform, its step comprises:
1) generate a tree-like metadata schema, its root node is the metadata base class that comprises the EJB base attribute, will comprise the child node of the metadata of neology as this tree-like metadata schema, and wherein the metadata of child node has been inherited above-mentioned base class;
2) above-mentioned metadata and note thereof are resolved;
3) Enterprise Java Bean container obtains the required category information in service at EJB by reading configuration file, and it is loaded, and finishes the deployment of EJB;
4) by the realization of specific transactions logic in the interceptor module support Enterprise Java Bean container, Enterprise Java Bean container obtains above-mentioned metadata and the defined resource of note thereof, realizes the expansion of Enterprise Java Bean container.
2. the method for Enterprise Java Bean container is characterized in that in the extension member operation support platform as claimed in claim 1, supports the AOP in the Enterprise Java Bean container to call by the interceptor method of life cycle readjustment and the interceptor method of business procedure.
3. the method for Enterprise Java Bean container is characterized in that in the extension member operation support platform as claimed in claim 1 or 2, and Enterprise Java Bean container obtains the interceptor chain in the Bean example; Create the interceptor chain of Bean type by the interceptor structure of Bean type; Create the interceptor chain of Bean example by the interceptor structure of Bean example; Call each method in the interceptor chain successively, realize the interceptor mechanism in the Enterprise Java Bean container.
4. the method for Enterprise Java Bean container is characterized in that in the extension member operation support platform as claimed in claim 3, by relying on the mode of injecting the resource of above-mentioned metadata and note definition thereof is injected Enterprise Java Bean container.
5. the method for Enterprise Java Bean container is characterized in that in the extension member operation support platform as claimed in claim 4, injects by field injection and setter the resource of above-mentioned metadata and note definition thereof is injected Enterprise Java Bean container.
6. the method for Enterprise Java Bean container is characterized in that in the extension member operation support platform as claimed in claim 4, and Enterprise Java Bean container injects described resource before the interceptor method that any operational approach or the life cycle of EJB example are adjusted back is called.
7. the method for Enterprise Java Bean container in the extension member operation support platform as claimed in claim 4, it is characterized in that, to rely on to inject by described interceptor module and realize, then this POJO be placed the top of interceptor chain of the PostConstruct type life cycle of each Enterprise Java Bean container as the interceptor of a system level as a POJO.
8. the method for Enterprise Java Bean container is characterized in that in the extension member operation support platform as claimed in claim 1, and the metadata of child node has directly or indirectly been inherited above-mentioned Enterprise Java Bean container base class.
9. the method for Enterprise Java Bean container in the extension member operation support platform as claimed in claim 1, it is characterized in that, by resolver above-mentioned metadata and note thereof are resolved, described resolver adopts hierarchical structure, ground floor includes attitude session Bean, no attitude session Bean and message-driven Bean resolver, the second layer comprises that class is explained, method is explained and resolver is explained in the territory, the 3rd layer of resolver that comprises certain concrete note, and resolver manages by its manager.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011101510671A CN102221998A (en) | 2011-06-07 | 2011-06-07 | Method for extending EJB container in component running support platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011101510671A CN102221998A (en) | 2011-06-07 | 2011-06-07 | Method for extending EJB container in component running support platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102221998A true CN102221998A (en) | 2011-10-19 |
Family
ID=44778559
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011101510671A Pending CN102221998A (en) | 2011-06-07 | 2011-06-07 | Method for extending EJB container in component running support platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102221998A (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102508668A (en) * | 2011-11-11 | 2012-06-20 | 西安交通大学 | AOP (Aspect Oriented Programming) implementation method of EJB 3 (Enterprise Java Beans 3) containers based on dynamic stack |
| CN103793232A (en) * | 2014-02-20 | 2014-05-14 | 浪潮集团山东通用软件有限公司 | Component calling and extending frame implementation method based on AOP |
| CN103873509A (en) * | 2012-12-12 | 2014-06-18 | 中国移动通信集团浙江有限公司 | EJB service overload protection method and system thereof |
| CN105700892A (en) * | 2016-02-22 | 2016-06-22 | 浪潮通用软件有限公司 | Component layering extension method based on inheritance relationship |
| CN107577712A (en) * | 2017-08-01 | 2018-01-12 | 武汉斗鱼网络科技有限公司 | The method, apparatus and computer equipment of a kind of loading page |
| CN108089904A (en) * | 2017-12-21 | 2018-05-29 | 上海新案数字科技有限公司 | A kind of displayed page extended method and equipment |
| WO2019227749A1 (en) * | 2018-05-29 | 2019-12-05 | 北京字节跳动网络技术有限公司 | Metadata container parsing method and apparatus, and storage medium |
| CN112162731A (en) * | 2020-10-13 | 2021-01-01 | 广州乐摇摇信息科技有限公司 | Data expansion method, device, storage medium and electronic device |
| CN112256351A (en) * | 2020-10-26 | 2021-01-22 | 卫宁健康科技集团股份有限公司 | Implementation method of Feign component, micro-service calling method and device |
| CN113448618A (en) * | 2020-03-26 | 2021-09-28 | 红帽公司 | Processing portable extensions at build time |
| JP2022119762A (en) * | 2014-10-08 | 2022-08-17 | スプランク インコーポレイテッド | Real-time reporting based on measurement of software |
| CN115794214A (en) * | 2023-02-09 | 2023-03-14 | 中邮消费金融有限公司 | Application module metadata management method, device, storage medium and device |
-
2011
- 2011-06-07 CN CN2011101510671A patent/CN102221998A/en active Pending
Non-Patent Citations (3)
| Title |
|---|
| 中间件产业技术创新战略联盟: "支持EJB2.X和EJB3.0规范的单容器系统设计与实现", 《四方国件》 * |
| 王梓又，周明辉，曹东刚，李瑞超，梅宏: "一种Java EE应用服务器的EJB3.0元数据框架", 《计算机工程与科学》 * |
| 范刚，曹东刚，周明辉，肖赞，梅宏: "一种良构可扩展的构件运行平台容器系统", 《中国科技论文在线》 * |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102508668B (en) * | 2011-11-11 | 2014-11-05 | 西安交通大学 | AOP (Aspect Oriented Programming) implementation method of EJB 3 (Enterprise Java Beans 3) containers based on dynamic stack |
| CN102508668A (en) * | 2011-11-11 | 2012-06-20 | 西安交通大学 | AOP (Aspect Oriented Programming) implementation method of EJB 3 (Enterprise Java Beans 3) containers based on dynamic stack |
| CN103873509B (en) * | 2012-12-12 | 2017-06-20 | 中国移动通信集团浙江有限公司 | A kind of EJB services overload protection method and system |
| CN103873509A (en) * | 2012-12-12 | 2014-06-18 | 中国移动通信集团浙江有限公司 | EJB service overload protection method and system thereof |
| CN103793232A (en) * | 2014-02-20 | 2014-05-14 | 浪潮集团山东通用软件有限公司 | Component calling and extending frame implementation method based on AOP |
| JP2022119762A (en) * | 2014-10-08 | 2022-08-17 | スプランク インコーポレイテッド | Real-time reporting based on measurement of software |
| JP7391137B2 (en) | 2014-10-08 | 2023-12-04 | スプランク インコーポレイテッド | Real-time reporting based on software measurements |
| CN105700892A (en) * | 2016-02-22 | 2016-06-22 | 浪潮通用软件有限公司 | Component layering extension method based on inheritance relationship |
| CN107577712A (en) * | 2017-08-01 | 2018-01-12 | 武汉斗鱼网络科技有限公司 | The method, apparatus and computer equipment of a kind of loading page |
| CN108089904B (en) * | 2017-12-21 | 2021-11-16 | 上海七十迈数字科技有限公司 | Display page expansion method and device |
| CN108089904A (en) * | 2017-12-21 | 2018-05-29 | 上海新案数字科技有限公司 | A kind of displayed page extended method and equipment |
| WO2019227749A1 (en) * | 2018-05-29 | 2019-12-05 | 北京字节跳动网络技术有限公司 | Metadata container parsing method and apparatus, and storage medium |
| US10979759B2 (en) | 2018-05-29 | 2021-04-13 | Beijing Bytedance Network Technology Co., Ltd. | Analysis method, device and storage medium of moov box |
| CN113448618A (en) * | 2020-03-26 | 2021-09-28 | 红帽公司 | Processing portable extensions at build time |
| CN112162731B (en) * | 2020-10-13 | 2021-10-22 | 广州乐摇摇信息科技有限公司 | Data expansion method, device, storage medium and electronic device |
| CN112162731A (en) * | 2020-10-13 | 2021-01-01 | 广州乐摇摇信息科技有限公司 | Data expansion method, device, storage medium and electronic device |
| CN112256351A (en) * | 2020-10-26 | 2021-01-22 | 卫宁健康科技集团股份有限公司 | Implementation method of Feign component, micro-service calling method and device |
| CN112256351B (en) * | 2020-10-26 | 2023-11-17 | 卫宁健康科技集团股份有限公司 | Method for realizing Feign component, method and device for calling micro-service |
| CN115794214A (en) * | 2023-02-09 | 2023-03-14 | 中邮消费金融有限公司 | Application module metadata management method, device, storage medium and device |
| CN115794214B (en) * | 2023-02-09 | 2023-05-12 | 中邮消费金融有限公司 | Application module metadata management method, device, storage medium and apparatus |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102221998A (en) | Method for extending EJB container in component running support platform | |
| Bergmayr et al. | A systematic review of cloud modeling languages | |
| Bruneliere et al. | Modisco: A model driven reverse engineering framework | |
| CA2777443C (en) | Automated enterprise software development | |
| Goncalves | Beginning Java EE 6 with GlassFish 3 | |
| US20090006987A1 (en) | Visual design tools for portal content creation | |
| CN101430644B (en) | System and method of executing a dynamic program in a structured environment | |
| CN112860260B (en) | Web-based cross-platform application construction tool and method in college scene | |
| CN102810057A (en) | Log recording method | |
| KR20140067018A (en) | Describing native application programming interfaces of an operating system with metadata | |
| CN111857801B (en) | Construction method of mobile application | |
| Hasselbring | Component-based software engineering | |
| Martinez et al. | Recovering sequence diagrams from object-oriented code: An ADM approach | |
| Henttonen et al. | Integrability and extensibility evaluation from software architectural models–A case study | |
| CN102508673A (en) | System and method for rapidly developing and configuring platform software | |
| CN104133678A (en) | Method and device for constructing and operating interactive seismic interpretation system | |
| Tran et al. | On the role and application of ontologies in information systems | |
| CN113342399B (en) | Method and device for configuring structure of application program and readable storage medium | |
| US20120159490A1 (en) | Dynamic scenarios for managing computer system entities | |
| CN103135972A (en) | Module repository, service development method and system based on module repository | |
| Wipp | Workflows on Android: A framework supporting business process execution and rule-based analysis | |
| Górski | Model-to-model transformations of architecture descriptions of an integration platform | |
| Kouamou | Building a service-oriented ERP from an open source software | |
| Zhou et al. | A lightweight component-based development approach for enterprise applications | |
| Hamann et al. | Towards supporting multiple execution environments for uml/ocl models at runtime |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20111019 |
|
| WD01 | Invention patent application deemed withdrawn after publication |