In some apps, these are the 2 main solutions.
I think dynamic sql isn’t industry-standardized (stored proc has an ANSI standard) and depends heavily on rdbms server support.
In theory, once microsoft/oracle has a good dynamic-sql feature, other vendors could follow.
Search for “dynamic sql oracle/sybase/db2/…”
Rule engines offer matching algorithms that can determine
– which rules need to be run and
– in which order,
timelocal (59,59,23,1,1, 0) # represents 23:59:59 on 1 Jan 2000. I think Time::Local can’t understand, can’t work with dates in 1900. Solution?
Date::Calc supports Year AD 1
condition-sharing is one of the simple but big benefits/justifications for rule engines.
http://www.infoq.com/articles/Rule-Engines # technical, not too high-level, not too abstract, very few mistakes pointed out by comments
I think a constant is a pre-defined name-value pair, different from a “literal” or “value”
J4: 10% of the non-trivial but /tractable/ beginner eclipse problems are related  to build-path. If you don’t mind studying “too much” on a topic, study build path.
Each source folder can define an exclusion-filter to specify which resources inside the folder should be invisible to the compiler.
offline help > Java Development User Guide > Reference > Property Pages > Java Build Path page
 indirectly, perhaps in hind sight