I'm actually wondering now if it really makes sense to do this toString stuff in openflowj or handle it at a higher level. I'm guessing the main reason those toString methods were added was to customize the string values that were returned in the floodlight REST API. But with BigDB we already have a custom serializer that does the default conversion to lower case and maps underscore to dash for enum values. And if we wanted to deviate from that behavior for some values we could always write custom serializers for particular enum types with exceptions for particular values. So I guess I'm leaning towards removing the toString overrides from openflowj. Well, maybe leaving in the generic support for overriding toString just in case we need it later but removing the current configuration for OFPortFeatures, OFPortState, and OFPortConfig. What do you think?