In order to remove the requirement to distribute the iText library /.jar with ICEfaces bundles, including src bundles, we need to refactor the ace:dataExporter PDF export feature to use reflective techniques to find, load, and access the iText library classes it requires. Doing so will avoid java compilation errors that would otherwise occur when building the ace:dataExporter component without the iText jar on the class path.

A good reference example of this technique is the icesoft/compat/core/src/main/java/com/icesoft/util/SeamUtilities.java class, which uses reflection extensively.

In addition, we should also add some nice logging so that if the PDF export is executed at runtime, and the iText library is not present on the classpath, it logs an error explaining the problem to the server console, and possibly also populates the ace:dataExporter message(s) with a nice user facing error, such as "PDF Export not available at this time. Contact your System Administrator." Under no circumstances do we want the application state to be corrupted or otherwise fouled.