I think I figured out the problem; passing in "null" by accident and canProcess failed rather then return false. Jody
On 13/04/2010, at 11:14 AM, Ben Caradoc-Davies wrote: > AppSchemaDataAccessFactory will ignore any configuration parameters map that > does not have "dbtype" set to "app-schema" and a "url" set. The problem is > that "url" should never be set to a property file for app-schema. Never, > ever. It should only ever point to an app-schema mapping file. Your stack > trace tells me that app-schema is trying to parse a property file as a > mapping file, likely because "url" points at it. This will fail. If my > understanding is correct, at the point your error occurs, app-schema is still > loading the mapping file, which it has to complete before it touches any data. > > Kind regards, > Ben. > > > On 12/04/10 18:41, Jody Garnett wrote: >> I think (on using the debugger) that the problem may be easier. There is a >> chance that the url passed in was null (or some internal eclipse "bundle" >> url) that the app schema code was tripping up on. So a couple test cases >> may be in order? >> >> Jody >> >> On 12/04/2010, at 5:59 PM, Ben Caradoc-Davies wrote: >> >>> I agree, this is likely to be the problem. >>> >>> From the tutorial: >>> http://docs.geoserver.org/trunk/en/user/data/app-schema/tutorial.html >>> >>> The mapping file refers to the directory containing the property file, and >>> reference the property file feature type by name. See: >>> https://svn.auscope.org/subversion/AuScope/geoserver/config/geoserver-app-schema-tutorial-config/trunk/workspaces/gsml/gsml_MappedFeature/gsml_MappedFeature.xml >>> >>> <sourceType>gsml_MappedFeature</sourceType> says get data from >>> gsml_MappedFeature.properties (and the rest of the file says look in the >>> same directory as the mapping file). >>> >>> Your error seems to suggest you have set your datastore.xml >>> connectionParameters "url" entry to point at the property file. >>> Particularly as the culprit is apache Digester, which is used to read the >>> mapping files. >>> >>> Kind regards, >>> Ben. >>> >>> >>> On 12/04/10 14:25, Rob Atkinson wrote: >>>> Are you trying to connect to a property file directly - not setting >>>> the data store to point to an XML config/mapping file which then >>>> references the property file? >>>> >>>> On Mon, Apr 12, 2010 at 3:46 PM, Jody Garnett<jody.garn...@gmail.com> >>>> wrote: >>>>> Hi Ben: >>>>> As mentioned I am hooking app schema and others up to uDig (depending on >>>>> the >>>>> DataAccessFinder contract to sort things out ...) - and I am running into >>>>> a >>>>> conflict with the app schema code.... >>>>> I am using a property file as my test file; in the hopes of connecting to >>>>> a >>>>> PropertyDataStore; and instead app schema is trying to connect and then >>>>> having a bad time... >>>>> Apr 12, 2010 3:34:19 PM org.geotools.data.complex.config.XMLConfigDigester >>>>> digest >>>>> SEVERE: parsing >>>>> bundleresource://41.fwk17890856/net/refractions/udig/catalog/geotools/data/test-data/sample_data.properties >>>>> org.xml.sax.SAXParseException: Content is not allowed in prolog. >>> >>> -- >>> Ben Caradoc-Davies<ben.caradoc-dav...@csiro.au> >>> Software Engineering Team Leader >>> CSIRO Earth Science and Resource Engineering >>> Australian Resources Research Centre >> >> > > > -- > Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> > Software Engineering Team Leader > CSIRO Earth Science and Resource Engineering > Australian Resources Research Centre ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
