(4) is designed only for the internal purposes for tooling, it is recommended that it is not used, not public api. (9) is missing a "connection-jndi-name" attribute, that defines the "jndi" name of the connection that your "Flims" model going use to gather the data. If in your case you implemented all the data gathering logic inside your translator "urequest", then in the Translator class (ExecutionFactory) you need to override the method "isSourceRequired" and return "false". That says to the VDB deployer that there is no external source where the data is read from, its all in the translator. Hope this helps. Ramesh.. On Tue, 2010-07-13 at 14:05 -0400, Charles Simon wrote: > I am having trouble getting past the VDBDeployer.validateServices() tests. > > If I add the<vdb> property "preview" as true it skips the > validateSources test but I don't know if that is the correct thing to do. > > My VDB XML file looks like this (line numbers on the left are not int > the file): > > 1)<?xml version="1.0" encoding="UTF-8" standalone="yes"?> > 2)<vdb name="UQDynamicFilms" version="1"> > 3)<property name="UseConnectorMetadata" value="true" /> > 4)<property name="preview" value="true" /> > 5) > 6)<model name="Films"> > 7)<property name="importer.useFullSchemaName" value="false"/> > 8)<property name="uqDBName" value="FILMS"></property> > 9)<source name="Films" translator-name="uquest"/> > 10)</model> > 11)</vdb> > > When I remove line 4 the VDB fails the validateSources() test and is set > inactive. > >