I am on 2.6.x not 2.5.x (so you may need to think when applying the
patches to 2.5.x?) I generated the patch with svn diff so it should
not be that effected by platform.
I have created a bug report here:
- http://jira.codehaus.org/browse/GEOT-2486
I will see if I can apply the changes to 2.5.x fo
I cannot apply your patches. All 3 files report errors when applying with
patch -p0 < patchfile
I am up to date with 2.5.x repository
No idea, I think you are sitting in front of an M$ box, I am working on a
linux box. Converting with dos2unix does not help either.
Can you try it agein aft
Just to follow up - Christian and I sorted out some things over IRC;
and he is reviewing a patch right now.
Jody
On Thu, May 14, 2009 at 10:52 PM, Jody Garnett wrote:
> Sorry my previous reply fell of the list ... here is a proposal for a
> "refreshed" Repository interface:
>
> public interface R
Sorry my previous reply fell of the list ... here is a proposal for a
"refreshed" Repository interface:
public interface Repository {
/**
* Search for the DataAccess (or DataStore) providing access
* to the indicated typeName.
*
* This lookup method is not namespace aware;
Jody I took a deeper look to Catalog interface and I got dazed and confused.
Again I agree on having a central repository interface but a redesign is not
a matter of adding some methods.
Some thoughts
1) I am missing the clean concept of namespace handling
2) It must be possible to write a
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 in
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
O
I wanted to use the org.geotools.data.Repository (life would be easier) but
this would not work for geoserver.
So I introduced the DataStoreLookup interface.
I did a special implementation for the geoserver catalog, look here. Perhaps
we have to do something similar for UDIG.
https://svn.cod
Thanks - excellent job on the documentation. I do see a conflict
between "org.geotools.data.gen.DataStoreLookup" and Repository. Is
this something we can do as the module moves to supported?
The docs for repository are here:
http://docs.codehaus.org/display/GEOTDOC/Managing+DataStores+using+Reposi
Christian Müller ha scritto:
>
>
> The modul matrix page is here
> http://docs.codehaus.org/display/GEOTOOLS/Feature-Pregeneralized
>
> At the moment, the module/documentation is located in the unsupported
> branches.
+1 for graduation
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo
The modul matrix page is here
http://docs.codehaus.org/display/GEOTOOLS/Feature-Pregeneralized
At the moment, the module/documentation is located in the unsupported
branches.
--
The NEW KODAK i700 Series Scanners
11 matches
Mail list logo
