A couple of comments - Having an interface to allow geotools to look up something in the geoserver catalog is the he point of the repository interface. So if geoserver has changed we need to ensure this interface is updated so geotools code can hook into it. - I do not really want the repository interface as it stands to block your work; lets modify it to suit your needs. - I do not really want duplicated work; you will need an implementation of your DataStoreLookup anyway to have test cases in geotools right?
So lets use your DataStoreLookup interface as a request to modify Repository. Does it represent exactly what you need ? Is it missing anything that is needed? Jody On Wed, May 13, 2009 at 10:41 PM, Andrea Aime <aa...@opengeo.org> wrote: > Christian Müller ha scritto: >> >> I wanted to use the org.geotools.data.Repository (life would be easier) >> but this would not work for geoserver. > > Wondering if it's not possible to make a GeoServer plugin that wraps > the GeoServer catalog into a Repository interface? > > Cheers > Andrea > > -- > Andrea Aime > OpenGeo - http://opengeo.org > Expert service straight from the developers. > ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
