Abstract: Computer-based methods and systems for deploying model-driven applications to an application server are described. Consistent with an embodiment of the invention, an application server includes a model deployment module that provides a model deployment service. The model deployment module receives as input a data model that serves as a single source of truth for an application. Based on the input model, the model deployment module configures the application server, for example, by automatically generating object-relational mapping logic that facilitates data persistence by mapping data elements in an object domain to data elements in a relational database domain. Additionally, the model deployment module generates a utility module that supports advanced modeling capabilities, including derived properties and constraints.

Abstract: Computer-based methods and systems for deploying model-driven applications to an application server are described. Consistent with an embodiment of the invention, an application server includes a model deployment module that provides a model deployment service. The model deployment module receives as input a data model that serves as a single source of truth for an application. Based on the input model, the model deployment module configures the application server, for example, by automatically generating object-relational mapping logic that facilitates data persistence by mapping data elements in an object domain to data elements in a relational database domain. Additionally, the model deployment module generates a utility module that supports advanced modeling capabilities, including derived properties and constraints.

Abstract: Interfacing communication between a non-hypertext transfer protocol (HTTP) event source and an application server function is described by calling a listener method to detect one or more events received from a non-HTTP event source. Data from the events is extracted and assembled into an application server event (AS Event) message. The AS Event message is transmitted to the application server function, which uses data from the AS Event to process its functionality. Resulting information may be sent to a communication method, which formats a message for the non-HTTP event source using the resulting information. This formatted message is then communicated to the non-HTTP event source. The interfaced communication may be initiated either by the non-HTTP event source or the application server function.