Good thoughts - I'm glad you are on board and thinking about the hard-to-track-down issues when implementations of interfaces differ in their behavior. I've not used the different hierarchies much, sticking mostly to XSSF, but I can see how this could lead to tricky bugs.
I'm personally partial to default methods in interfaces now that we are up to Java 8 for base support. That can help when the methods are well-defined and don't need much instance state in cases where we want/need further class distinctions and hierarchy on one branch of the implementations but not others. Moving to a common superclass locks in things that maybe we want left more flexible. I don't have an example off the top for POI, but I've seen that other places. However, if there is enough common behavior that it requires significant instance state to perform, default methods become harder to maintain and a superclass starts to look more appealing. Looking forward to your suggestions and discussion topics. Greg On Fri, Jan 4, 2019 at 1:41 PM Vladislav Galas <[email protected]> wrote: > Actually value/type conversion logic could (and should, imho) be moved to > a superclass. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
