Is this a generic design pattern? "Descriptor"?

Question

Am I doing this under a common design pattern? If so, what is the name?

I have a complex object that has “simple” fields, such as strings and line lists, as well as other complex objects. I want to add instances of this object to the JMS message queue, which means they should be Serializable. I don’t want to create an entire object chart Serializable, so instead I selected Descriptor objects that contain the necessary information to create complex objects and Builder objects that can create objects. Now I serialize the Descriptor object and add it to the queue. When an object is deleted, it is embedded in a full-fledged object using "Builder".

It is important to note that objects are tasks performed on other systems. Message queuing is one way, and serialization occurs only at the beginning of the job's life cycle.

Answer 1

The most similar template with the one you implemented looks like Memento .

In this case, he used to store the state of the object in Memento , while everything can change the original object and allows you to restore the old state, using Memento as the "previous state" of your object.

, , , , .

Answer 2

, () Memento pattern.