[
https://issues.redhat.com/browse/WFLY-1415?page=com.atlassian.jira.plugin...
]
David Lloyd commented on WFLY-1415:
-----------------------------------
As the original poster (7 years ago!), I feel I should provide a point of clarification.
IIRC, it transpires that string switch also creates a distinct class as well; my
recollection should be checked because it would be a bit of a wasted effort to do all this
migration only to discover that nothing was saved.
Move away from expensive enum switch
------------------------------------
Key: WFLY-1415
URL:
https://issues.redhat.com/browse/WFLY-1415
Project: WildFly
Issue Type: Task
Reporter: David Lloyd
Priority: Minor
Labels: janitor
We use enums and enum switch extensively. These constructs generate many, many
additional classes and bloat the code base unnecessarily.
All cases where we are using enum-based switches for our XML parsers should be converted
to use Java 7 String switch instead. The enum values shall be replaced with String
constant fields, all enum switches converted to String switches, and all enum types
removed from these classes. The net result should be a reduction by dozens if not
hundreds of .class files, and possibly a measurable performance boost as well.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)