Abstract: In accordance with an embodiment, described herein is a system and method for providing cross-microservice query processing. The system provides an object service framework that supports the use of microservices that may be loosely-coupled but related in some way, for example in that they interoperate together or require access to each other's data in order to process queries. Each microservice can be developed, deployed and evolve independently, and interact with the other microservices through contracts or interfaces that are defined as public APIs and are then exposed via the framework. The object service framework can be used, for example to provide a cross-microservice layer that automatically transforms queries that join objects in different microservices into a single database query that is optimized for use with the database.

Abstract: In accordance with an embodiment, described herein is a system and method for providing cross-microservice query processing. The system provides an object service framework that supports the use of microservices that may be loosely-coupled but related in some way, for example in that they interoperate together or require access to each other's data in order to process queries. Each microservice can be developed, deployed and evolve independently, and interact with the other microservices through contracts or interfaces that are defined as public APIs and are then exposed via the framework. The object service framework can be used, for example to provide a cross-microservice layer that automatically transforms queries that join objects in different microservices into a single database query that is optimized for use with the database.

Abstract: In accordance with an embodiment, described herein is a system and method for providing cross-microservice query processing. The system provides an object service framework that supports the use of microservices that may be loosely-coupled but related in some way, for example in that they interoperate together or require access to each other's data in order to process queries. Each microservice can be developed, deployed and evolve independently, and interact with the other microservices through contracts or interfaces that are defined as public APIs and are then exposed via the framework. The object service framework can be used, for example to provide a cross-microservice layer that automatically transforms queries that join objects in different microservices into a single database query that is optimized for use with the database.

Abstract: Techniques are provided for encapsulating a user experience design for user interfaces of an application, where the user experience design comprises a look and feel of the application and a plurality of functional elements of the application. A plurality of rules for implementing the one or more user interfaces may be defined, and the rules may be based at least in part on the user experience design. Additionally, a pattern may be generated based at least in part on the plurality of rules. The pattern may be deployed to a distributed network of computing devices, and reused in the design of multiple other applications. The new user interfaces for those applications may be generated based at least in part on the pattern, where the additional applications comply with the look and feel and the plurality of functional elements of the other applications that share the pattern.

Abstract: Simplifying understanding of procedure dependencies in a form definition used in user interfaces. In an embodiment, a form definition including a set of procedures (identified by a corresponding identifier) are examined to determine pairs of procedures such that a caller procedure of a pair invokes/refers a called procedure in the pair. For each of pair of procedures determined, a link associated with an identifier identifying the called procedure is included in the caller procedure. The link is designed to display the called procedure in response to a user action associated with the identifier in a display of the caller procedure.

Abstract: Techniques are provided for encapsulating a user experience design for user interfaces of an application, where the user experience design comprises a look and feel of the application and a plurality of functional elements of the application. A plurality of rules for implementing the one or more user interfaces may be defined, and the rules may be based at least in part on the user experience design. Additionally, a pattern may be generated based at least in part on the plurality of rules. The pattern may be deployed to a distributed network of computing devices, and reused in the design of multiple other applications. The new user interfaces for those applications may be generated based at least in part on the pattern, where the additional applications comply with the look and feel and the plurality of functional elements of the other applications that share the pattern.

Abstract: Techniques are provided for encapsulating a user experience design for user interfaces of an application, where the user experience design comprises a look and feel of the application and a plurality of functional elements of the application. A plurality of rules for implementing the one or more user interfaces may be defined, and the rules may be based at least in part on the user experience design. Additionally, a pattern may be generated based at least in part on the plurality of rules. The pattern may be deployed to a distributed network of computing devices, and reused in the design of multiple other applications. The new user interfaces for those applications may be generated based at least in part on the pattern, where the additional applications comply with the look and feel and the plurality of functional elements of the other applications that share the pattern.

Abstract: Techniques are provided for encapsulating a user experience design for user interfaces of an application, where the user experience design comprises a look and feel of the application and a plurality of functional elements of the application. A plurality of rules for implementing the one or more user interfaces may be defined, and the rules may be based at least in part on the user experience design. Additionally, a pattern may be generated based at least in part on the plurality of rules. The pattern may be deployed to a distributed network of computing devices, and reused in the design of multiple other applications. The new user interfaces for those applications may be generated based at least in part on the pattern, where the additional applications comply with the look and feel and the plurality of functional elements of the other applications that share the pattern.

Abstract: A method of tracking dependencies in an application file, including analyzing the application file to identify at least one dependency in the application file, extracting information from the application file related to the dependency to allow identification of an entity to which the application file has a dependency from the information, and storing the dependency for the application file in the application tier data dictionary. A system has a memory, at a first tier, to store an application tier data dictionary and at least one application file, and a processor at the first tier to determine dependencies in the application file, store the dependencies in the application tier data dictionary, communicate with a second tier, separate from the first tier, as needed to access information with regard to the dependencies, and store the information in the application tier data dictionary.

Abstract: A method of tracking dependencies in an application file, including analyzing the application file to identify at least one dependency in the application file, extracting information from the application file related to the dependency to allow identification of an entity to which the application file has a dependency from the information, and storing the dependency for the application file in the application tier data dictionary. A system has a memory, at a first tier, to store an application tier data dictionary and at least one application file, and a processor at the first tier to determine dependencies in the application file, store the dependencies in the application tier data dictionary, communicate with a second tier, separate from the first tier, as needed to access information with regard to the dependencies, and store the information in the application tier data dictionary.

Abstract: Simplifying understanding of procedure dependencies in a form definition used in user interfaces. In an embodiment, a form definition including a set of procedures (identified by a corresponding identifier) are examined to determine pairs of procedures such that a caller procedure of a pair invokes/refers a called procedure in the pair. For each of pair of procedures determined, a link associated with an identifier identifying the called procedure is included in the caller procedure. The link is designed to display the called procedure in response to a user action associated with the identifier in a display of the caller procedure.

Abstract: An explosion-proof type rotating electrical machine having excellent cooling and brush powder discharge capabilities. A drive shaft of a rotor is provided with slip rings for supplying current to a field coil, which is energized through brushes capable of activating the field coil by contacting with the slip rings. The brush compartment incorporated with the brushes and slip rings and the outside of the rotating electrical machine are connected with each other through an air suction path, the brush compartment and an inside space of the rotating electrical machine are connected with each other through an air blowing path, in which a flame stifling wire net is provided.