Method, apparatus and systems thereof for implementing non-function logic extensibly

An apparatus for implementing non-function logic for a plurality of applications extensibly and independently of functional logic for each one of the plurality of applications, comprising:

• at least one processor;
• and
• an application loader for loading policy demand configuration of an application;
• a policy attacher for acquiring association relationship between a policy and a plug-in required by the application based on a loaded policy demand configuration of the application, and for generating a plug-in context definition according to the acquired association relationship, the plug-in context definition being part of a plug-in context associated with the plug-in, wherein the plug-in context defines services provided by the plug-in and reference to other plug-ins related to the plug-in;
• an application builder for generating an application runtime object based on a component definition and generating a plug-in context object based on the plug-in context definition, wherein the plug-in context object is an instantiated plug-in context definition;
• an application constructor unit for associating the plug-in context object to the application runtime object so as to implement a function of the plug-in for the application;
• and
• a plug-in registry unit for storing a plug-in registry containing information on description of the plug-ins and on relationships between the plug-ins;
• wherein the policy attacher acquires the association relationship between the policy and the required plug-in by querying the plug-in registry based on the policy demand configuration.

A system for separating functional logic of an application from non-function logic for any of a plurality of applications and implementing the non-function logic, including:

• a central processing unit;
• an application runtime layer entity configured to implement functional logic by user and utilize plug-ins provided by an infrastructure service plug-in layer entity;
• the infrastructure service plug-in layer entity configured to implement the plug-in by utilizing services provided by an application runtime layer entity;
• and
• the application runtime layer entity configured to implement acquiring an association relationship between a policy and a plug-in required by the application based on a loaded policy demand configuration of the application by querying a plug-in registry containing information on description of the plug-ins and on relationships between the plug-ins based on the policy demand configuration, and further performing steps of:
• generating a plug-in context definition according to the acquired association relationship, the plug-in context definition being part of a plug-in context associated with the plug-in, wherein the plug-in context defines services provided by the plug-in and reference to other plug-ins related to the plug-in;
• generating an application runtime object based on a component definition;
• generating a plug-in context object based on the plug-in context definition, wherein the plug-in context object is an instantiated plug-in context definition;
• and
• associating the plug-in context object to the application runtime object so as to implement a function of the plug-in for the application.