Abstract: Computer code is received that is written using a dynamic Domain Specific Language (DSL) running in a General Purpose Language (GPL) computing environment. A compiler performs static compiler analysis on the computer code. The static compiler analysis includes referencing a security policy defining one or more unacceptable program behaviors. During compile time at the compiler, runtime security checking functionality is performed leveraging compiler extensions, type information, and environment specific compile context. Results of the static compiler analysis are used to indicate when execution of the computer code would result in performance of the one or more unacceptable program behaviors. The one or more unacceptable program behaviors include modifying preexisting computer code to incorporate the computer code written using the DSL.

Abstract: Pieces of an entity's data set can be related with each other using a canonical Uniform Resource Locator (URL). If a server returns pieces of an entity's data record to a client within multiple separate REST-based responses, the client can discern from the canonical URL that those pieces relate to the same entity. In response to each REST-based request from a client, a server returns, with the client-requested data, a canonical URL that uniquely identifies that data's entity. A client can receive the canonical URL with the data that the server returns. If the canonical URLs returned along with data items in separate requests match, then the client determines that those data items pertain to the same entity. If the client determines that separately received data items pertain to the same entity, then the client can merge those data items together into a unified record that the client stores locally.

Abstract: Computer code is received that is written using a dynamic Domain Specific Language (DSL) running in a General Purpose Language (GPL) computing environment. A compiler performs static compiler analysis on the computer code. The static compiler analysis includes referencing a security policy defining one or more unacceptable program behaviors. During compile time at the compiler, runtime security checking functionality is performed leveraging compiler extensions, type information, and environment specific compile context. Results of the static compiler analysis are used to indicate when execution of the computer code would result in performance of the one or more unacceptable program behaviors. The one or more unacceptable program behaviors include modifying preexisting computer code to incorporate the computer code written using the DSL.

Abstract: An example system and method for securing computer code of a dynamic Domain Specific Language (DSL) that leverages a General Purpose Language (GPL). An example method includes enhancing compile-time security enforcement functionality for computer code written using the DSL, in part by using a compiler to perform static analysis on the DSL computer code. The static analysis includes referencing a security policy defining one or more unacceptable program behaviors; and indicating when execution of the computer code would result in performance of the one or more unacceptable program behaviors based on results of the static analysis.

Abstract: An example system and method for securing computer code of a dynamic Domain Specific Language (DSL) that leverages a General Purpose Language (GPL). An example method includes enhancing compile-time security enforcement functionality for computer code written using the DSL, in part by using a compiler to perform static analysis on the DSL computer code. The static analysis includes referencing a security policy defining one or more unacceptable program behaviors; and indicating when execution of the computer code would result in performance of the one or more unacceptable program behaviors based on results of the static analysis.

Abstract: Various arrangements for debugging logic being executed by a webserver is presented. A virtual machine of the webserver may execute runtime threads for a plurality of remote users. The web server may compile business logic code received from a developer computer system via a web-based interface into an logic insight injected code. The logic insight injected code may be compiled from the business logic code to include debugging functionality. The virtual machine of the webserver may execute the logic insight injected code concurrently with the runtime threads being executed for the plurality of remote users. The debugging functionality of the logic insight injected code being executed may not affect execution of the runtime threads for the plurality of users.

Abstract: Various arrangements for debugging logic being executed by a webserver is presented. A virtual machine of the webserver may execute runtime threads for a plurality of remote users. The web server may compile business logic code received from a developer computer system via a web-based interface into an logic insight injected code. The logic insight injected code may be compiled from the business logic code to include debugging functionality. The virtual machine of the webserver may execute the logic insight injected code concurrently with the runtime threads being executed for the plurality of remote users. The debugging functionality of the logic insight injected code being executed may not affect execution of the runtime threads for the plurality of users.

Abstract: A system is provided that automatically manages data consistency of a web application. When the system sends a data entity to a user interface component that the system has determined is an updatable user interface component, the system stores a version indicator for the data entity within a resource scope. When the system receives a request to update the data entity, the system compares the version indicator stored within the resource scope with a version indicator stored within a data store. When the two version indicators are identical, the system updates the data entity. When the two version indicators are not identical, the system raises an exception.

Abstract: Various arrangements for debugging logic being executed by a webserver is presented. A virtual machine of the webserver may execute runtime threads for a plurality of remote users. The web server may compile business logic code received from a developer computer system via a web-based interface into an logic insight injected code. The logic insight injected code may be compiled from the business logic code to include debugging functionality. The virtual machine of the webserver may execute the logic insight injected code concurrently with the runtime threads being executed for the plurality of remote users. The debugging functionality of the logic insight injected code being executed may not affect execution of the runtime threads for the plurality of users.

Abstract: Systems and methods for debugging domain specific languages are provided. In accordance with an embodiment, one such system can comprise a web which includes a virtual machine, a debug execution machine, and a domain specific language (DSL)-specific tool interface. The web server is configured to compile DSL code received from a developer computer. During compilation the DSL code is instrumented to include debugging information received from the developer computer. The web server is also configured to execute, by the virtual machine, the instrumented code. During execution the instrumented code communicates with the debug execution machine such that a state of the debug execution machine mirrors a state of the virtual machine.

Abstract: Various arrangements for implementing a security policy at runtime are presented. A plurality of calls in a syntax tree may be identified. Each call of the plurality of calls may be substituted with a corresponding security-modified call to create a plurality of security-modified methods calls. Each security-modified call may be linked with a security class. Following modification of each call of the plurality of calls, the plurality of security-modified calls may be compiled into bytecode.

Abstract: Pieces of an entity's data set can be related with each other using a canonical Uniform Resource Locator (URL). If a server returns pieces of an entity's data record to a client within multiple separate REST-based responses, the client can discern from the canonical URL that those pieces relate to the same entity. In response to each REST-based request from a client, a server returns, with the client-requested data, a canonical URL that uniquely identifies that data's entity. A client can receive the canonical URL with the data that the server returns. If the canonical URLs returned along with data items in separate requests match, then the client determines that those data items pertain to the same entity. If the client determines that separately received data items pertain to the same entity, then the client can merge those data items together into a unified record that the client stores locally.

Abstract: A system is provided that automatically manages data consistency of a web application. When the system sends a data entity to a user interface component that the system has determined is an updatable user interface component, the system stores a version indicator for the data entity within a resource scope. When the system receives a request to update the data entity, the system compares the version indicator stored within the resource scope with a version indicator stored within a data store. When the two version indicators are identical, the system updates the data entity. When the two version indicators are not identical, the system raises an exception.

Abstract: Systems and methods for debugging domain specific languages are provided. In accordance with an embodiment, one such system can comprise a web which includes a virtual machine, a debug execution machine, and a domain specific language (DSL)-specific tool interface. The web server is configured to compile DSL code received from a developer computer. During compilation the DSL code is instrumented to include debugging information received from the developer computer. The web server is also configured to execute, by the virtual machine, the instrumented code. During execution the instrumented code communicates with the debug execution machine such that a state of the debug execution machine mirrors a state of the virtual machine.

Abstract: Various arrangements for debugging logic being executed by a webserver is presented. A virtual machine of the webserver may execute runtime threads for a plurality of remote users. The web server may compile business logic code received from a developer computer system via a web-based interface into an logic insight injected code. The logic insight injected code may be compiled from the business logic code to include debugging functionality. The virtual machine of the webserver may execute the logic insight injected code concurrently with the runtime threads being executed for the plurality of remote users. The debugging functionality of the logic insight injected code being executed may not affect execution of the runtime threads for the plurality of users.

Abstract: Various arrangements for implementing a security policy at runtime are presented. A plurality of calls in a syntax tree may be identified. Each call of the plurality of calls may be substituted with a corresponding security-modified call to create a plurality of security-modified methods calls. Each security-modified call may be linked with a security class. Following modification of each call of the plurality of calls, the plurality of security-modified calls may be compiled into bytecode.

Abstract: A system that pushes active data to a client receives a first request for a page that includes active data from the client. The active data includes a component and a corresponding model for a data source of the component. The system determines if the model is active and if so, instantiates an encoder that corresponds to the component. The system queries the model for the active data and renders a user interface representation of the data. The system then returns a response to the request with the user interface representation.

Abstract: A system that pushes active data to a client receives a first request for a page that includes active data from the client. The active data includes a component and a corresponding model for a data source of the component. The system determines if the model is active and if so, instantiates an encoder that corresponds to the component. The system queries the model for the active data and renders a user interface representation of the data. The system then returns a response to the request with the user interface representation.