java builder类,对Java Builder类进行子类化

最新推荐文章于 2021-09-04 20:19:00 发布

weixin_39759989

最新推荐文章于 2021-09-04 20:19:00 发布

阅读量67

点赞数

文章标签： java builder类

在Builder模式中，当需要为基类的Builder添加子类功能时，可能会遇到构建顺序错误的问题。文章提出了一种解决方案，即通过泛型确保Builder方法返回的类型与子类Builder一致，从而强制正确的构建顺序。具体做法是将基类Builder方法的返回类型设为泛型T，并在子类中指定T为子类Builder。这样，调用者必须按照正确的顺序调用子类的Builder方法，避免了错误的构建顺序导致的失败。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Give this Dr Dobbs article, and the Builder Pattern in particular, how do we handle the case of subclassing a Builder? Taking a cut-down version of the example where we want to subclass to add GMO labelling, a naive implementation would be:

public class NutritionFacts {

private final int calories;

public static class Builder {

private int calories = 0;

public Builder() {}

public Builder calories(int val) { calories = val; return this; }

public NutritionFacts build() { return new NutritionFacts(this); }

}

protected NutritionFacts(Builder builder) {

calories = builder.calories;

}

Subclass:

public class GMOFacts extends NutritionFacts {

private final boolean hasGMO;

public static class Builder extends NutritionFacts.Builder {

private boolean hasGMO = false;

public Builder() {}

public Builder GMO(boolean val) { hasGMO = val; return this; }

public GMOFacts build() { return new GMOFacts(this); }

}

protected GMOFacts(Builder builder) {

super(builder);

hasGMO = builder.hasGMO;

}

Now, we can write code like this:

GMOFacts.Builder b = new GMOFacts.Builder();

b.GMO(true).calories(100);

But, if we get the order wrong, it all fails:

GMOFacts.Builder b = new GMOFacts.Builder();

b.calories(100).GMO(true);

The problem is of course that NutritionFacts.Builder returns a NutritionFacts.Builder, not a GMOFacts.Builder, so how do we solve this problem, or is there a better Pattern to use?

Note: this answer to a similar question offers up the classes I have above; my question is regarding the problem of ensuring the builder calls are in the correct order.

解决方案

You can solve it using generics. I think this is called the "Curiously recurring generic patterns"

Make the return type of the base class builder methods a generic argument.

public class NutritionFacts {

private final int calories;

public static class Builder {

private int calories = 0;

public Builder() {}

public T calories(int val) {

calories = val;

return (T) this;

}

public NutritionFacts build() { return new NutritionFacts(this); }

}

protected NutritionFacts(Builder builder) {

calories = builder.calories;

}

Now instantiate the base builder with the derived class builder as the generic argument.

public class GMOFacts extends NutritionFacts {

private final boolean hasGMO;

public static class Builder extends NutritionFacts.Builder {

private boolean hasGMO = false;

public Builder() {}

public Builder GMO(boolean val) {

hasGMO = val;

return this;

}

public GMOFacts build() { return new GMOFacts(this); }

}

protected GMOFacts(Builder builder) {

super(builder);

hasGMO = builder.hasGMO;

}