-
Improvement
-
Resolution: Fixed
-
Normal
-
None
-
s12
-
None
We have these Fake DFDL schema objects (defined in dsom.Types.scala), and they are risky. There is a fake SchemaSet for example.
Now the way OOLAG works is that it accumulates diagnostic objects on the "root" component of the schema components. That root could be this Fake SchemaSet for example, and then error messages would accumulate there, and (1) be lost (2) never be reclaimed. The Fakes is a scala object, so a global mutable variable.
Change so that using say, Fakes.fakeSD, creates a new SchemaDocument object each time. I.e., make it a factory for new fake schema components, not a singleton set of fixed shared ones.