I've not done much with the vtests before but looking at TUSCANY-2291 i wondered if there's a consistent way the vtests should handle testing exceptions? The CallbackTestCase currently uses ServiceFinder class from vtest utilities but other vtests that do exceptions like destroy test handle everything themselves and use the new SCANode2Factory code. Is there a "standard" way vtests should be doing this?
...ant
