Abstract: Utilizing a JAVASCRIPT Object Notation (JSON) bridge during JAVA-based composite application development can begin with the receipt of a command to present the wiring diagram of a JAVA-based composite application by an enhanced JAVA-based composite application development tool. The JAVA-based composite application can consist of one or more JAVA-based components and non-JAVA-based components, with one property of a JAVA-based component being communicatively wired to a non-JAVA-based component. A JSON bridge can acknowledge the accessing of the JAVA-based composite application. The wiring diagram of the JAVA-based composite application can then be visually rendered. For the property of the JAVA-based component communicatively wired to the non-JAVA-based component, a user-selectable option to utilize the JSON bridge for communication can be presented.

Abstract: A method and system for cross-screen component communication in dynamically created composite applications. Meta-data in the mark-up for a source component (e.g. eXtensible Markup Language—XML information) in a dynamically created composite application includes indications of which screens target components are located on. These indications are contained in definitions of logical connections established between components referred to as “cross-page wire” definitions. Executable objects, referred to as “cross-page wire” executable objects, are generated based on the cross-page wire definitions in the source component mark-up. The cross-page wire executable objects are executed by a run-time entity, such as a “property broker” or the like, in response to a change in a property value for which the cross-page wire has been defined, in order to deliver a new value of that property to one or more target components located on screens different from the screen on which the source component is located.

Abstract: A method and system for cross-screen component communication in dynamically created composite applications. Meta-data in the mark-up for a source component (e.g. eXtensible Markup Language—XML information) in a dynamically created composite application includes indications of which screens target components are located on. These indications are contained in definitions of logical connections established between components referred to as “cross-page wire” definitions. Executable objects, referred to as “cross-page wire” executable objects, are generated based on the cross-page wire definitions in the source component mark-up. The cross-page wire executable objects are executed by a run-time entity, such as a “property broker” or the like, in response to a change in a property value for which the cross-page wire has been defined, in order to deliver a new value of that property to one or more target components located on screens different from the screen on which the source component is located.