Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 3
    However, would you put complex business logic in an enum? For example, transactions, I/O, etc? I don't have an argument against it, but I have the feeling something is not right, that enums are not for complex business transactions. Commented Oct 8, 2021 at 19:54
  • 3
    But by putting the logic into the enum, this logic would be exposed to clients who (have to) know the enum. Isn't this exposing too much? Or would you make those methods just accessible inside the package? Commented Oct 9, 2021 at 0:46
  • 1
    @PaŭloEbermann: we're looking at a web service here. It's called via HTML. The client only has to know the name of the enum constants, and the value it sends is mapped by the web framework (see the RequestParameter annotation) to the enum. Commented Oct 9, 2021 at 16:12
  • 1
    Still, an enum can be use as property type in a DTO, in a model object, in a function parameter, etc. And this one carries with it all the power of a service layer operation that basically can be accessed anywhere the enum value goes. I just don't think that is a good design. Commented Oct 10, 2021 at 15:49