Dynamic model reflection

Abstract

A method that includes obtaining, by an application executing on a computing system, a list of properties defining at least one property. The executing application writes an uncompiled class definition implementing a compiled interface and writes one or more properties of the compiled interface into the uncompiled class definition. The executing application writes the at least one property and at least one serialization attribute into the uncompiled class definition. The executing application causes the uncompiled class definition to be compiled, loads the compiled class definition, and creates an object by instantiating the compiled class definition. The object is serializable. The executing application may reflect on the compiled interface to obtain the one or more properties. Each of the one or more properties is strongly typed.

1 . (canceled) 
     
     
         2 . A computer-implemented method comprising:
 receiving a data stream corresponding to a dynamic object associated with one or more properties of a strong type, the data stream including serialized data according to a serialization method;   identifying a class definition of the dynamic object according to the data stream, the class definition including a serialization attribute;   converting the data stream into a new object, wherein converting the data stream into the new object includes instantiating the class definition, and wherein the new object is identical to the object; and   performing a strongly typed operation on the new object without writing additional code.   
     
     
         3 . The method of  claim 2 , wherein performing the strongly typed operation does not trigger a runtime error. 
     
     
         4 . The method of  claim 2 , wherein the serialization attribute corresponds to the serialization method. 
     
     
         5 . The method of  claim 2 , wherein the class definition further includes non-serialization attribute indicating one or more properties that are not to be serialized. 
     
     
         6 . The method of  claim 2 , wherein the properties of the strong type are associated with an interface associated with a limited set of attributes. 
     
     
         7 . The method of  claim 2 , wherein the properties are written to the class definition prior to compilation. 
     
     
         8 . The method of  claim 2 , wherein the properties are obtained according to reflection by the executing application. 
     
     
         9 . The method of  claim 2 , wherein a state of the new object corresponds to a state of the dynamic object according to the serialized data, and wherein the strongly typed operation changes the state of the new object. 
     
     
         10 . The method of  claim 2 , wherein a list of the properties is obtained from a first data store, and wherein the class definition is written to a second data store. 
     
     
         11 . A system comprising:
 a communication interface that receives a data stream corresponding to a dynamic object associated with one or more properties of a strong type, the data stream including serialized data according to a serialization method; and   a processor that executes an executing application stored in memory, wherein the processor executes the executing application to:
 identify a class definition of the dynamic object according to the data stream, the class definition including a serialization attribute; 
 convert the data stream into a new object, wherein converting the data stream into the new object includes instantiating the class definition, and wherein the new object is identical to the object; and 
 perform a strongly typed operation on the new object without writing additional code. 
   
     
     
         12 . The system of  claim 11 , wherein the processor performing the strongly typed operation does not trigger a runtime error. 
     
     
         13 . The system of  claim 11 , wherein the serialization attribute corresponds to the serialization method. 
     
     
         14 . The system of  claim 11 , wherein the class definition further includes non-serialization attribute indicating one or more properties that are not to be serialized. 
     
     
         15 . The system of  claim 11 , wherein the properties of the strong type are associated with an interface associated with a limited set of attributes. 
     
     
         16 . The system of  claim 11 , wherein the properties are written to the class definition prior to compilation. 
     
     
         17 . The system of  claim 11 , wherein the properties are obtained according to reflection by the executing application. 
     
     
         18 . The system of  claim 11 , wherein a state of the new object corresponds to a state of the dynamic object according to the serialized data, and wherein the strongly typed operation changes the state of the new object. 
     
     
         19 . The system of  claim 11 , wherein a list of the properties is obtained from a first data store, and wherein the class definition is written to a second data store. 
     
     
         20 . A non-transitory, computer-readable storage medium, having embodied thereon a program executable by a processor to perform a method comprising:
 receiving a data stream corresponding to a dynamic object associated with one or more properties of a strong type, the data stream including serialized data according to a serialization method;   identifying a class definition of the dynamic object according to the data stream, the class definition including a serialization attribute;   converting the data stream into a new object, wherein converting the data stream into the new object includes instantiating the class definition, and wherein the new object is identical to the object; and   performing a strongly typed operation on the new object without writing additional code.   
     
     
         21 . The non-transitory, computer-readable storage medium of  claim 20 , wherein performing the strongly typed operation does not trigger a runtime error. 
     
     
         22 . The non-transitory, computer-readable storage medium of  claim 20 , wherein the serialization attribute corresponds to the serialization method. 
     
     
         23 . The non-transitory, computer-readable storage medium of  claim 20 , wherein the class definition further includes non-serialization attribute indicating one or more properties that are not to be serialized. 
     
     
         24 . The non-transitory, computer-readable storage medium of  claim 20 , wherein the properties of the strong type are associated with an interface associated with a limited set of attributes. 
     
     
         25 . The non-transitory, computer-readable storage medium of  claim 20 , wherein the properties are written to the class definition prior to compilation. 
     
     
         26 . The non-transitory, computer-readable storage medium of  claim 20 , wherein the properties are obtained according to reflection by the executing application. 
     
     
         27 . The non-transitory, computer-readable storage medium of  claim 20 , wherein a state of the new object corresponds to a state of the dynamic object according to the serialized data, and wherein the strongly typed operation changes the state of the new object. 
     
     
         28 . The non-transitory, computer-readable storage medium of  claim 20 , wherein a list of the properties is obtained from a first data store, and wherein the class definition is written to a second data store.