Methods and apparatus for dynamic endpoint generators and dynamic remote object discovery and brokerage
View Patent ↗The system and method disclosed herein is a dynamic endpoint generator that enables a client device or application to consume business objects. The business objects are dynamic business objects whose definitions can be changed by either adding or removing data or actions without the need to involve technical or development resources to reconfigure or recompile the actual objects. The endpoint generator provides updated endpoint information automatically without the need for manual generation of endpoint or contract data. If a business object is modified or newly added, the endpoint generator is automatically notified and publishes information about the modified or newly added object. The client device that is accessing the business object is notified about the modified or newly added object. Or, an endpoint is generated when a client device requests a business object.
1. A method of generating a dynamic endpoint allowing a client device to consume a business object, the endpoint including an address, a binding, and a contract, the method comprising:
loading a definition of the business object, the definition having properties and methods;
iterating through the definition;
mapping the definition to endpoint-supported protocols, the mapping including:
(i) mapping the business object properties to data contracts;
(ii) mapping the business object methods to operation contracts; and
(iii) ensuring business object method signatures have endpoint-supported inputs and outputs; and
generating the endpoint based on a configuration, the configuration including services configuration, Windows Communication Foundation (“WCF”) configuration, representational state transfer (“REST”) configuration, and managed configuration;
wherein the endpoint is generated in response to at least one of (a) the client device requesting the business object, (b) the business object being created and (c) the business object being updated.
2. The method of claim 1 , further including generating .NET endpoints for use in a WCF framework and generating Atom, XML, and JSON endpoints for use in a REST framework.
3. The method of claim 1 , wherein the business object belongs to a category, and the endpoint is generated for the category.
4. The method of claim 1 , wherein the protocol configuration overrides the services configuration and the managed configuration overrides the protocol configuration.
5. The method of claim 1 , wherein the endpoint is configured based upon a user selection.
6. The method of claim 1 , wherein managed configuration includes configuring whether a static endpoint is generated for the business object and whether the endpoint is isolated.
7. The method of claim 6 , wherein the isolation includes at least one of (i) memory isolation, (ii) address isolation and (iii) security binding isolation.
8. The method of claim 6 , wherein configuring the isolation allows configuring at least one of (i) whether a server rebuilds all endpoints on the server or (ii) whether the server rebuilds less than all of the endpoints on the server.
9. A non-transitory computer readable medium storing instructions for generating a dynamic endpoint allowing a client device to consume a business object, the endpoint including an address, a binding, and a contract, the instructions causing a computing device to:
load a definition of the business object, the definition having properties and methods;
iterate through the definition;
map the definition to endpoint-supported protocols, the mapping including:
(i) mapping the business object properties to data contracts,
(ii) mapping the business object methods to operation contracts, and
(iii) ensuring business object method signatures have endpoint-supported inputs and outputs; and
generate the endpoint based on a configuration, the configuration including services configuration, Windows Communication Foundation (“WCF”) configuration, representational state transfer (“REST”) configuration, and managed configuration;
wherein the endpoint is generated in response to at least one of (a) the client device requesting the business object, (b) the business object being created and (c) the business object being updated.
10. The non-transitory computer readable medium of claim 9 , the instructions further causing the computing device to generate .NET endpoints for use in a WCF framework and generate Atom, XML, and JSON endpoints for use in a REST framework.
11. The non-transitory computer readable medium of claim 9 , wherein the business object belongs to a category, and the endpoint is generated for the category.
12. The non-transitory computer readable medium of claim 9 , wherein the protocol configuration overrides the services configuration and the managed configuration overrides the protocol configuration.
13. The non-transitory computer readable medium of claim 9 , wherein the endpoint is configured based upon a user selection.
14. The non-transitory computer readable medium of claim 9 , wherein managed configuration includes configuring whether a static endpoint is generated for the business object and whether the endpoint is isolated.
15. The non-transitory computer readable medium of claim 14 , wherein the isolation includes at least one of (i) memory isolation, (ii) address isolation and (iii) security binding isolation.
16. The non-transitory computer readable medium of claim 14 , wherein configuring the isolation allows configuring at least one of (i) whether a server rebuilds all endpoints on the server or (ii) whether the server rebuilds less than all of the endpoints on the server.
17. A system for generating a dynamic endpoint allowing a client device to consume a business object, the endpoint including an address, a binding, and a contract comprising a processor structured to cause the system to:
load a definition of the business object, the definition having properties and methods;
iterate through the definition;
map the definition to endpoint-supported protocols, the mapping including:
(i) mapping the business object properties to data contracts,
(ii) mapping the business object methods to operation contracts, and
(iii) ensuring business object method signatures have endpoint-supported inputs and outputs; and
generate the endpoint based on a configuration, the configuration including services configuration, Windows Communication Foundation (“WCF”) configuration, representational state transfer (“REST”) configuration, and managed configuration;
wherein the endpoint is generated in response to at least one of (a) the client device requesting the business object, (b) the business object being created and (c) the business object being updated.
18. The system of claim 17 , the processor structured to further cause the system to generate .NET endpoints for use in a WCF framework and generate Atom, XML, and JSON endpoints for use in a REST framework.
19. The system of claim 17 , wherein the business object belongs to a category, and the endpoint is generated for the category.
20. The system of claim 17 , wherein the protocol configuration overrides the services configuration and the managed configuration overrides the protocol configuration.
21. The system of claim 17 , wherein the endpoint is configured based upon a user selection.
22. The system of claim 17 , wherein managed configuration includes configuring whether a static endpoint is generated for the business object and whether the endpoint is isolated.
23. The system of claim 22 , wherein the isolation includes at least one of (i) memory isolation, (ii) address isolation and (iii) security binding isolation.
24. The system of claim 22 , wherein configuring the isolation allows configuring at least one of (i) whether a server rebuilds all endpoints on the server or (ii) whether the server rebuilds less than all of the endpoints on the server.