class explosion

How can I avoid a combinatorial explosion of readers?

I'm building a Spring Batch application that originally had five database readers for five different data types. I now need to support XML and CSV sources as well…