DDEX (data designer extensibility) default object implementations for software development processes
First Claim
1. A method implemented within a computer system that includes at least one processor and memory storing instructions which, when executed by the at least one processor, implement the method for determining an implementation for a Data Designer Extensibility (DDEX) support entity, the method comprising:
- a computer system, which includes at least one processor, receiving a request from a client for an instance of a DDEX support entity, the DDEX support entity corresponding to a DDEX support entity definition that includes;
an interface that represents a contract between clients calling the DDEX support entity and any implementations of the interface, wherein the contract comprises one or more method definitions that define one or more tasks performed by the DDEX support entity, the one or more method definitions implemented by the implementations of the interface; and
metadata comprising i) an attribute that indicates the existence of a default implementation for the DDEX support entity and ii) an identifier that uniquely identifies the default implementation;
the computer system querying a first DDEX provider for a provider-specific implementation for the DDEX support entity;
in response to the query, the computer system determining that the first DDEX provider lacks the provider-specific implementation for the DDEX support entity;
the computer system determining that the metadata includes the attribute that indicates the existence of the default implementation for the DDEX support entity;
the computer system using the identifier to look up the default implementation;
the computer system instantiating an instance of the default implementation; and
the computer system returning the instance of the default implementation to the client.
2 Assignments
0 Petitions
Accused Products
Abstract
A system and method for providing DDEX (data designer extensibility) default object implementations by bundling information associated with a support entity and information required to instantiate a new default instance is provided. Metadata associated with the definition of the support entity indicates if a default implementation exists and includes information associated with the creation of the default implementation. The metadata of the support entity is analyzed to automatically create and return a default implementation if the provider does not supply a specific implementation.
-
Citations
14 Claims
-
1. A method implemented within a computer system that includes at least one processor and memory storing instructions which, when executed by the at least one processor, implement the method for determining an implementation for a Data Designer Extensibility (DDEX) support entity, the method comprising:
-
a computer system, which includes at least one processor, receiving a request from a client for an instance of a DDEX support entity, the DDEX support entity corresponding to a DDEX support entity definition that includes; an interface that represents a contract between clients calling the DDEX support entity and any implementations of the interface, wherein the contract comprises one or more method definitions that define one or more tasks performed by the DDEX support entity, the one or more method definitions implemented by the implementations of the interface; and metadata comprising i) an attribute that indicates the existence of a default implementation for the DDEX support entity and ii) an identifier that uniquely identifies the default implementation; the computer system querying a first DDEX provider for a provider-specific implementation for the DDEX support entity; in response to the query, the computer system determining that the first DDEX provider lacks the provider-specific implementation for the DDEX support entity; the computer system determining that the metadata includes the attribute that indicates the existence of the default implementation for the DDEX support entity; the computer system using the identifier to look up the default implementation; the computer system instantiating an instance of the default implementation; and the computer system returning the instance of the default implementation to the client. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A computer system for implementing a method for determining an implementation for a Data Designer Extensibility (DDEX) support entity, the computer system comprising:
-
at least one processor; and one or more computer storage media having stored thereon computer executable instructions that, when executed by the at least one processor, implement the method, comprising; the computer system receiving a request from a client for an instance of a DDEX support entity, the DDEX support entity corresponding to a DDEX support entity definition that includes; an interface that represents a contract between clients calling the DDEX support entity and any implementations of the interface, wherein the contract comprises one or more method definitions that define one or more tasks performed by the DDEX support entity, the one or more method definitions implemented by the implementations of the interface; and metadata comprising i) an attribute that indicates the existence of a default implementation for the DDEX support entity and ii) an identifier that uniquely identifies the default implementation; the computer system querying a first DDEX provider for a provider-specific implementation for the DDEX support entity; in response to the query, the computer system determining that the first DDEX provider lacks the provider-specific implementation for the DDEX support entity; the computer system determining that the metadata includes the attribute that indicates the existence of the default implementation for the DDEX support entity; the computer system using the identifier to look up the default implementation; the computer system instantiating an instance of the default implementation; and
the computer system returning the instance of the default implementation to the client.
-
-
14. One or more computer storage media having stored thereon computer executable instructions that, when executed by at least one processor of a computer system, implement a method for determining an implementation for a Data Designer Extensibility (DDEX) support entity, the method comprising:
-
a computer system, which includes at least one processor, receiving a request from a client for an instance of a DDEX support entity, the DDEX support entity corresponding to a DDEX support entity definition that includes; an interface that represents a contract between clients calling the DDEX support entity and any implementations of the interface, wherein the contract comprises one or more method definitions that define one or more tasks performed by the DDEX support entity, the one or more method definitions implemented by the implementations of the interface; and metadata comprising i) an attribute that indicates the existence of a default implementation for the DDEX support entity and ii) an identifier that uniquely identifies the default implementation; the computer system querying a first DDEX provider for a provider-specific implementation for the DDEX support entity; in response to the query, the computer system determining that the first DDEX provider lacks the provider-specific implementation for the DDEX support entity; the computer system determining that the metadata includes the attribute that indicates the existence of the default implementation for the DDEX support entity; the computer system using the identifier to look up the default implementation; the computer system instantiating an instance of the default implementation; and the computer system returning the instance of the default implementation to the client.
-
Specification