In some sense, a nullary constructor _must_ be sufficient.  That is to
say, in the most general sense you must assume that bean instances will
be initialized by invocation of a nullary constructor (and no other).
Bean classes are required to have one, and it is poor practice and will
cause you problems if that constructor does not leave the new instance
in a consistent, well-defined state.

With that out of the way, there are two non-exclusive possibilities:

1) Refactor your bean into two or more beans.  It is often the case when
a class has complex initialization requirements that the class itself is
too broad in scope.

2) Define class-wide defaults by use of static methods and variables.
This is bit of a kludge, and it has potential to get you into trouble,
but it can be made to work.  The nullary constructor then uses the class
methods and variables to help initialize new instances.

John Bollinger
jobollin@indiana.edu