Impact - Parsing Methodology
The file parsing is handled using StringTokenizer - which is a Java 1.0 approach and replaced in more recent java with Regex type approaches.
It appears the each of the panes implements its own .in file parser (using StrngTokenizer) and that there are discrepancies in some of the implementations. I found that models that loaded OK in the Processor threw exceptions when opened in the PostProcessor module. I found that by moving the all but ELEMENT and NODE blocks to the top of the file removed these exceptions. Later when I went back and attempted to reprocess the changed .in files in the Processor stage I got loading/parsing exceptions.
As a result of this I am experimenting with replacing the parser code with implementations using Regex.