Hi, sorry for cross posting, but this is a problem affecting geoserver.
I don't have much time as to get deeper on this right now, but just wanted to
know if the transitive dependency on gml datastore carried out by
gt2-validation->gt2-directory->gt2-gml is alright or something that should be
just for test scope.
In any case it is forcing geoserver to include the gml datastore, and in turn,
the gml datastore factory is catching up every set of datastore parameters
that has a "url" key (I know it is circumstantial and the same could be
caused by any other file datastore that expects no "dbtype" like parameter).
In any case, should we make a compendium of all available datastore parameters
and look for incompatibilities? or force all datastores to have a dbtype
parameter?
Gabriel
If I remember correctly the dependency from directory on gml ( and
shapefile ) are just used for testing. They should probably be changed
to be of scope "test". Not sure this will help us just developing in
eclipse though... but for release it should make it so that they are not
included.
Gabriel Roldán wrote:
Hi, sorry for cross posting, but this is a problem affecting geoserver.
I don't have much time as to get deeper on this right now, but just wanted to
know if the transitive dependency on gml datastore carried out by
gt2-validation->gt2-directory->gt2-gml is alright or something that should be
just for test scope.
In any case it is forcing geoserver to include the gml datastore, and in turn,
the gml datastore factory is catching up every set of datastore parameters
that has a "url" key (I know it is circumstantial and the same could be
caused by any other file datastore that expects no "dbtype" like parameter).
In any case, should we make a compendium of all available datastore parameters
and look for incompatibilities? or force all datastores to have a dbtype
parameter?
Gabriel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:1004,45e6df4a80021510810322!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Also how did the directory datastore get in to our default GeoServer distribution? I tried it out and it doesn't work at all, asks you for a list of extensions but then can't read the input at all, says it can't get a String from the text.
Justin Deoliveira wrote:
If I remember correctly the dependency from directory on gml ( and
shapefile ) are just used for testing. They should probably be changed
to be of scope "test". Not sure this will help us just developing in
eclipse though... but for release it should make it so that they are not
included.
Gabriel Roldán wrote:
Hi, sorry for cross posting, but this is a problem affecting geoserver.
I don't have much time as to get deeper on this right now, but just wanted to know if the transitive dependency on gml datastore carried out by gt2-validation->gt2-directory->gt2-gml is alright or something that should be just for test scope.
In any case it is forcing geoserver to include the gml datastore, and in turn, the gml datastore factory is catching up every set of datastore parameters that has a "url" key (I know it is circumstantial and the same could be caused by any other file datastore that expects no "dbtype" like parameter).
In any case, should we make a compendium of all available datastore parameters and look for incompatibilities? or force all datastores to have a dbtype parameter?
Gabriel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
Chris Holmes ha scritto:
Also how did the directory datastore get in to our default GeoServer distribution? I tried it out and it doesn't work at all, asks you for a list of extensions but then can't read the input at all, says it can't get a String from the text.
Bleah, afaik it's no more in the main pom, so we should not have it around, once fixed the transitive dependency from validation.
As far as why it's not working, it's because the factory pretends
a String parameter for the extensions instead of a comma separated plain String.
If we want to support directory data store, we need to either
change that parameter, or to make Geoserver handle String parameters.
Cheers
Andrea