Description Andy Ed 2010-12-07 04:38:45 EST

As an Epsilon ETL specification become more complex it can be difficult to trace the source of the bugs that give rise to exceptions. For example the following scenario describes one situation where it can be difficult to determine the root cause of an exception. When using the equivalent() or ::=, the translator tries unsuccesfully to create an element. This element may be deeply nested and difficult to locate when debugging. The error gives rise to a null pointer exception which is reported to have occurred at the point where the equivalent() is applied. This, however, does not indicate the source of the problem; i.e. the element which the translator was unable to create.

Reporting an Epsilon trace in addition to a Java stack trace at the time of such a failure would improve usability of the tool, especially with translations that are more complex. An Epsilon trace would help the user identify the point at which the tranlator failed.