Since the runtime does not provide a spec-compliant API for non-SCA clients to look up services, vtest test clients should now be using the vtest-provided ServiceFinder wrapper class. There is a small handful of vtests still using the Tuscany-specific APIs such as those provided by SCADomain and SCANode2Factory but the plan is to eventually move those to the wrapper class as well after some issues specific to those test cases are resolved.
Let me know if I did not answer your question. -- Kevin On Fri, May 23, 2008 at 10:32 AM, ant elder <[EMAIL PROTECTED]> wrote: > 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 >
