The verifier has three outputs... System.out/err, the .txt file and the .xml file.
Most of the time, this is okay.. The user runs the verifier and can read the txt
or have a program read the xml file to give them info about the validity of
If the archive is bogus for some reason, like the archive is an ejb-jar file
with no beans defined in the ejb-jar.xml then the user only gets output on
System.out/err. This makes integrating the verifier into tools harder, since a
tool would need to have TWO parsers to to make sure the user found out about
what the verifier was trying to say to the user:
one for the xml file (which is very easy to write)
and another to read the System.out/err streams (which is a bit more challenging)
I would like to see: Errors going onto the txt file and xml file output channel
as well as System.out/err...