On Mar 24, 2009, at 10:08 AM, Bob Morley wrote:
One thing that has come up is situations where we have entries in our
controller that reference missing screens and/or screens that
reference
missing widgets (mostly forms). What I wanted to do was create a unit
tester that would walk the controller path and find missing
references.
Has anyone does this before or have any thoughts?
The WebTools ArtifactInfo stuff does something like this (not sure if
it will meet your needs). It does parse and load all of the various
artifacts in OFBiz and in the initialization log shows warnings about
missing things (bad references) like this.
-David
