On 01/06/2010, at 1:08 PM, Ben Caradoc-Davies wrote:
> On 01/06/10 10:40, Jody Garnett wrote:
>> I thought I would take a look at app schema resolver to see how it is used;
>> thus far looking at test cases I cannot see how to bundle my own schema up
>> in jar form.
>
> Please see the GS user manual:
> http://docs.geoserver.org/trunk/en/user/data/app-schema/app-schema-resolution.html#classpath
>
> Examples of how to make schema jars using maven are in
> modules/unsupported/app-schema/app-schema-packages subdirectories.
>
> The full documentation of the path convention is in the javadoc for
> AppSchemaResolver.getSimpleHttpresourcePath(URI).
Thanks that is the link I was missing; will add a jumping off point in geotools
pointing there.
I also noted the description of the module was missing from the pom.xml - I am
not sure we are running mvn site these days so perhaps it is not that important?
>> I also cannot find any docs on the geotools site. I am fine if you want to
>> have the build of your configuration instructions on the geoserver site; the
>> requirement for a page showing a code example is still in place. And is a
>> good opportunity to link to where ever you are storing documentation.
>
> Can we use the new doc framework? It will be much easier to manage code
> examples written in sphinx.
We quickly covered this prior to justin's current proposal - the was between a
single doc directory; or a doc directory per module depending on how we want to
run things.
So we will need to sort out how to organise the user guide so that it can be
used by people to document their modules. My focus will be on the initial
welcome material in the short term.
Do you have any suggestions or ideas?
I would consider starting out by replacing the current module matrix page
(which also does not list any app schema modules) with rst files.
> The best classpath example is AppSchemaConfigurationTest.classpath . Creating
> a Configuration is the central step. Note that real use must add a GML 3.1
> GMLConfiguration as a dependency in the constructor. Yes, this should go in
> the library user manual (which I think is your meaning in asking this
> question).
As part of moving to supported we needed one wiki page with a code example :-)
So where should we put app schema (and how many plugins are marked. Currently
they are still in unsupported so I will put a placeholder there with the code
you provided.
>
> /**
> * Test we can {...@link Schemas#findSchemas(Configuration)} with
> classpath only.
> */
> @Test
> public void classpath() {
> Configuration configuration = new
> AppSchemaConfiguration("urn:cgi:xmlns:CGI:GeoSciML:2.0",
> "http://www.geosciml.org/geosciml/2.0/xsd/geosciml.xsd";, new
> AppSchemaResolver());
> SchemaIndex schemaIndex = Schemas.findSchemas(configuration);
> Assert.assertEquals(3, schemaIndex.getSchemas().length);
> String schemaLocation =
> schemaIndex.getSchemas()[0].getSchemaLocation();
> Assert.assertTrue(schemaLocation.startsWith("jar:file:"));
> Assert.assertTrue(schemaLocation.endsWith("geosciml.xsd"));
> }
>
> Kind regards,
>
> --
> Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au>
> Software Engineering Team Leader
> CSIRO Earth Science and Resource Engineering
> Australian Resources Research Centre
------------------------------------------------------------------------------
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
