Automatic connections between application components
First Claim
1. A computer-implemented method, comprising:
- receiving information by a running application identifying a first application component, the first application component having a set of code including a first set of one or more class members that can be connected to a second set of one or more class members of a second application component;
identifying a first class member of the first application component based, at least in part, on a first metadata tag related to the first class member, the first class member being one of a sink and a source, wherein the first metadata tag includes a connection-order designation, which indicates an order in which the first class member should be ranked as compared to other class members of the first application component when determining whether first-class-member code of the first class member should be integrated with another class member;
automatically selecting a second class member for the second application component, the second application component residing in the running application, the second class member being the other of the sink and the source; and
connecting the first class member with the second class member by integrating code, which is executable to carry out the first class member, into a runtime environment of the running application, so that information can be exchanged between the first application component and the second application component.
2 Assignments
0 Petitions
Accused Products
Abstract
One or more aspects of the subject matter described in this disclosure include identifying a first application component received by a running application, identifying a first automatically connectable connection for the first application component, selecting a second automatically connectable connection for a second application component, the second application component residing in the running application, and automatically connecting the first connection with the second connection so that information can be exchanged between the first application component and the second application component by way of the first connection and the second connection while the first application is running.
-
Citations
30 Claims
-
1. A computer-implemented method, comprising:
-
receiving information by a running application identifying a first application component, the first application component having a set of code including a first set of one or more class members that can be connected to a second set of one or more class members of a second application component; identifying a first class member of the first application component based, at least in part, on a first metadata tag related to the first class member, the first class member being one of a sink and a source, wherein the first metadata tag includes a connection-order designation, which indicates an order in which the first class member should be ranked as compared to other class members of the first application component when determining whether first-class-member code of the first class member should be integrated with another class member; automatically selecting a second class member for the second application component, the second application component residing in the running application, the second class member being the other of the sink and the source; and connecting the first class member with the second class member by integrating code, which is executable to carry out the first class member, into a runtime environment of the running application, so that information can be exchanged between the first application component and the second application component. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A computer program product, encoded on a non-transitory computer-readable medium, operable to cause one or more processors to perform operations comprising:
-
receiving information by a running application identifying a first application component, the first application component having a set of code including a first set of one or more class members that can be automatically bound to a second set of one or more class members of a second application component; automatically identifying a first class member for the first application component based, at least in part, on a first metadata tag related to the first class member, the first class member being one of a sink and a source, wherein the first metadata tag includes a binding-order designation, which indicates an order in which the first class member should be ranked as compared to other class members of the first application component when determining whether the first class member should be programmatically bound to another class member; automatically selecting a second class member for the second application component, the second application component residing in the running application, the second class member being the other of the sink and the source; and automatically programming a persistent bound connection between the first class member and the second class member so that information can be exchanged between the first application component and the second application component by using an application framework. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20)
-
-
21. A system comprising:
-
a machine-readable storage device including a program product; and one or more processors operable to execute the program product, interact with a display device, and perform operations comprising; receiving information by a running application identifying a first application component, the first application component having a set of code including a first set of one or more class members that can be programmatically bound to a second set of one or more class members of a second application component; automatically identifying a first class member for the first application component based, at least in part, on a first metadata tag related to the first class member, the first class member being one of a sink and a source, wherein the first metadata tag includes a binding-order designation, which indicates an order in which the first class member should be ranked as compared to other class members of the first application component when determining whether the first class member should be programmatically bound to another class member; automatically selecting a second class member for the second application component, the second application component residing in the running application, the second class member being the other of the sink and the source; and automatically programming a persistent bound connection between the first class member and the second class member so that information can be exchanged between the first application component and the second application component. - View Dependent Claims (22, 23, 24, 25, 26, 27, 28, 29, 30)
-
Specification