Re: Enum, switch, and a null
Wojtek wrote:
So then the get would return an already instantiated class? What about
threading? Would not all threads then get the same instance?
That's why I mentioned the Class<? extends SQL> option, duhy.
This is part of a Web app. Lots of threads...
Or is dbMap created for each use. That means I would be creating an
extra object (the map), plus an extra object for each DB engine, but
only using one of the engines for the life of the app.
Create it with the scope you desire. You only need to instantiate what you
use, but at least you won't have miles of hard-coding to deal with each
situation. Plus, you'd only instantiate the Class objects for the Map that
are specified in your deployment, so you would only have "an extra object for
each DB engine" that you want, not for all the world.
It's just an alternative, but the specific objections you raise are pretty
minor and easily handled. Personally I'll take an unnoticeable reduction in
run-time performance any time if it creates more maintainable code, which
moving things out of hard-coding generally does.
--
Lew