设计模式袖珍版连续转载之Factory.docVIP

设计模式袖珍版 连续转载之- Factory The easier van mistakes ? Tha t every one has done detailed work have experienee greatly, on the contrary, the higher the officer is done, saying the more abstract and general, fan error possibility is the less? As if we could，ve learned in life from the program? Ha ha. Use the factory method Attention should be paid to several characters, first you have to define product interface, as Sample, the product with the Sample under the interface in terface implementation class, such as SampleA, second to have a factory class, used to produce the product Sample, the following figure, most the right side is the production of Sample objects: A further complication is the expansion of the factory class, which also inherits its implementation class, concreteFactory. The abstract factory There is a Factory Method: the Factory Method Abstract Factory. The differenee between these two patterns is the complexity of creating objects? If the method for creating an object becomes more complex, as in the factory method above, we create an object Sample, if we have a new product interface Sample2? Lets assume: Sample has two concrete classes SampleA and SamleB, and Sample2 also has two concrete classes Sample2A and SampleB2 So, we will in the above example Factory into an abstract class, part of the encapsulation together in an abstract class, use subclasses implement different parts, the following is the Factory to expand into the abstract Factory in the above example: Public abstract class Factory { Public abstract Sample creator (); Public abstract Sample2 creator (String name); Public class SimpleFactory extends Factory { Public Sample creator () { Return new SampleA Public Sample2 creator (String name) { Return new Sample2A Public class BombFactory extends Factory { Public Sample creator () { Return new SampleB Public Sample2 creator (String name) { Return new Sample2B From above, you can see that the two factories each produce one set of Sample and Sample