Abstract: This disclosure provides various embodiments for providing transparently stateful execution of stateless applications. A request associated with an application is received and includes at least one operation to be executed by the application as well as a set of first state information. The application determines if the operations are to be executed statelessly or not. If the application is to be executed statelessly, the first state information is retrieved from the request and used to initialize the application. If not, then the first state of the application is retrieved from a location other than the received request. The operations are then executed by the application in the application's appropriate first state. A response including the relevant information associated with the response as well as an updated set of state information identifying the application's second state is generated and transmitted to the client.

Abstract: This disclosure provides various embodiments for providing transparently stateful execution of stateless applications. A request associated with an application is received and includes at least one operation to be executed by the application as well as a set of first state information. The application determines if the operations are to be executed statelessly or not. If the application is to be executed statelessly, the first state information is retrieved from the request and used to initialize the application. If not, then the first state of the application is retrieved from a location other than the received request. The operations are then executed by the application in the application's appropriate first state. A response including the relevant information associated with the response as well as an updated set of state information identifying the application's second state is generated and transmitted to the client.

Abstract: Methods and systems, including computer program products, implementing techniques for upgrading pattern configurations. The techniques include receiving configuration for a pattern, determining whether the configuration is current with respect to the pattern, automatically upgrading the configuration if the configuration is not current, and using the configuration to modify one or more predefined elements of an application.

Abstract: Methods and apparatus, including computer program products, implement techniques for structuring applications into reusable components. A reusable component having an external interface and an internal interface is implemented. The component encapsulates functionality, where multiple instances of the component are reusable at the same time. The component is configurable to embed one or more specified components. The external interface comprises an external programming interface, an external data-binding interface, and an external visual interface. The internal interface comprises an embedding interface, an internal programming interface, an internal data-binding interface, and an internal visual interface. The embedding interface specifies one or more component interfaces of components that can be embedded.

Abstract: Methods and apparatus, including computer program products, for storing and using customization data. A repository contains one or more repository objects, one or more variants for each repository object, and one or more layers for each variant. Each repository object has one or more model entities. The variants for each repository object are arranged in a first hierarchy, and the layers for each variant are arranged in a second hierarchy. Each layer includes a set of customization values, each customization value corresponding to one of the model entities. Customization values can be (but need not be) provided for each model entity in each layer and in each variant. The variants and layers can be arranged in order of specificity. A customization value for a model entity can be retrieved by locating the most specific variant and the most specific layer that contains a customization value for the model entity.

Abstract: Methods and apparatus including computer program products implement techniques for developing and deploying applications using configurable patterns. Configuration data is received for a pattern, and the configuration data is stored in a design store. The pattern defines an arrangement of user interface elements and specifies predefined actions that can be performed using the user interface elements. The configuration data specifies associations between one or more of the user interface elements or one or more objects in a back-end system. The configuration data is transferred from the design store to a design time repository, and the application is deployed corresponding to the configuration data.