当前位置：文江博客话题详情

java 特性还是 mixins 模式？

发布于 2024-07-08 12:58:54 字数 73 浏览 6 评论 0原文

有没有办法在java中模拟mixin或traits？基本上，我需要一种方法来进行多重继承，以便我可以将通用业务逻辑添加到多个类中

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

小情绪 2024-07-15 12:58:54

不是你想要的方式。 Effective Java 建议您“优先选择组合而不是继承”。这意味着您将通用逻辑移至其他类和委托。这就是解决 java 中缺乏多重继承的问题的方法。

回复收藏 0 原文

你丑哭了我 2024-07-15 12:58:54

我会将所有业务逻辑封装到一个新类 BusinessLogic 中，并让每个需要 BusinessLogic 的类调用该类。如果您的类需要调用 BusinessLogic 的单根层次结构，则还必须创建一个接口（BusinessLogicInterface？），

用伪代码

interface BusinessLogicInterace
{
    void method1();
    void method2();
}

class BusinessLogic implements BusinessLogicInterface
{
    void method1() { ... }
    void method2() { ... }
}

class User 
    extends OtherClass 
    implements BusinessLogicInterface
{
    BusinessLogic logic = new BusinessLogic();

    @Override
    void method1() { logic.method1(); }

    @Override
    void method2() { logic.method2(); }
}

表示：并不是解决缺乏多重继承的最漂亮的实现，并且当接口有很多方法时它会变得相当麻烦。最有可能的是，您需要尝试重新设计代码以避免需要 mixin。

I would encapsulate all of the business logic into a new class BusinessLogic and have each class that needs BusinessLogic make calls to the class. If you need a single rooted heirarchy for your classes that make calls to BusinessLogic, you'll have to create an interface as well (BusinessLogicInterface?)

In pseudo-code:

interface BusinessLogicInterace
{
    void method1();
    void method2();
}

class BusinessLogic implements BusinessLogicInterface
{
    void method1() { ... }
    void method2() { ... }
}

class User 
    extends OtherClass 
    implements BusinessLogicInterface
{
    BusinessLogic logic = new BusinessLogic();

    @Override
    void method1() { logic.method1(); }

    @Override
    void method2() { logic.method2(); }
}

This isn't the prettiest implementation to work around a lack of multiple inheritance and it becomes quite cumbersome when the interface has a lot of methods. Most likely, you'll want to try and redesign your code to avoid needing mixins.

回复收藏 0 原文

ゃ懵逼小萝莉 2024-07-15 12:58:54

今天，物体纯粹主义者在你心中激荡吗？

您认为您可以进行一些面向复合的编程吗？

那么您，先生，正在寻找Apache Polygene（以前名为 Qi4J，后来更名为 Zest 和/或 Apache-Zest）；）

更新 2022； 目前已停产，但无论如何还是有用的。

回复收藏 0 原文

倥絔 2024-07-15 12:58:54

您可以利用接口允许嵌套类（自动公共静态）这一事实来将接口方法的默认实现封装在接口本身中。即，将 Alex B 示例的 BusinessLogic 类移至界面内。

这类似于 Scala 为特征生成 JVM 代码的方式，如此处所述 Scala 特征如何编译成 Java 字节码？

当这样做时，示例变成：

interface BusinessLogicInterface {
    void method0();

    class DefaultImpl {
        private DefaultImpl() {
        }

        public static void method1(BusinessLogicInterface self) { ... }
        public static void method2(BusinessLogicInterface self) { ... }
    }

    void method1();
    void method2();
}

class User extends OtherClass implements BusinessLogicInterface {
    @Override
    void method0() { ... }

    @Override
    void method1() { BusinessLogic.defaultImpl.method1(this); }

    @Override
    void method2() { BusinessLogic.defaultImpl.method2(this); }
}

请注意，我们将接口类型的对象作为“self”参数传递。这意味着业务逻辑可以使用其他抽象方法（method0）。这对于使用彼此正交的抽象方法和可以根据这些正交方法实现的实用程序“扩展”方法创建特征非常有用。

缺点是每个接口都必须复制/粘贴样板委托代码。 Java 中另一个经常使用的模式没有这个缺点（但内聚性较低，调用方法的 OO 方式也较少）是创建一个具有复数名称的类作为包含静态方法的接口，这在 Collections 实用程序类中使用。

You can exploit the fact that interfaces allow nested classes (automatically public static) to keep the default implementation of the interface methods encapsulated within the interface itself. I.e. move the BusinessLogic class of Alex B's example inside the interface.

This is similar to the way Scala generates the JVM code for traits as explained here How are Scala traits compiled into Java bytecode?

When doing this the example becomes:

interface BusinessLogicInterface {
    void method0();

    class DefaultImpl {
        private DefaultImpl() {
        }

        public static void method1(BusinessLogicInterface self) { ... }
        public static void method2(BusinessLogicInterface self) { ... }
    }

    void method1();
    void method2();
}

class User extends OtherClass implements BusinessLogicInterface {
    @Override
    void method0() { ... }

    @Override
    void method1() { BusinessLogic.defaultImpl.method1(this); }

    @Override
    void method2() { BusinessLogic.defaultImpl.method2(this); }
}

Note that we pass an object of the interface type as the "self" parameter. This means the business logic can use other abstract methods (method0). This can be very useful for creating a trait with abstract methods that are all orthogonal to each other and utility "extension" methods that may be implemented in terms of these orthogonal methods.

The drawback is that each interface must copy/paste the boilerplate delegation code. Another often used pattern in Java without this drawback (but with less cohesion and less OO way to call the methods) is to create a class with the plural name as the interface containing the static methods, this is used in the Collections utility class.

回复收藏 0 原文