you know this a really basic question …(im just a OpenGeo user (Geoserver- gwc - OpenLayer) )
there is a way to run a process (bach script, python script, etc) to migrate the data_dir from 1.7.x to 2.0.0
i dont know something like this
python migrate.py ./1.7.7/data_dir ./2.0.0/data_dir
actually i work with 1.7.7 (with very good results :)), i create all my data_dir with python using the postgis metadata table geometry_columns …
but i cant do this with data_dir (2.0.0) because any entity or at least styles include an id number (StyleInfoImpl–46dbec34:125896aab6e:-7fec)
… i dont know if i can create this ids number manually (i dont try yet…)
- this automated scripts helpme when i have thousands of postgis layers…
PD: sorry for my bad english
gretting
Rodolfo B.
Hi Rodolfo,
Unfortunately there is not really. The only way really is to start geoserver 2.0.x on the 1.7.x data directory and have it automatically generate the 2.0.x version.
That said the format is more or less straight forward so you could script it. And yes you can make up your own identifiers as long as they are of course unique, and that any references are maintained (eg layer referencing styles).
Another thing you may be interested in looking at is the rest api which allows one to configure a geoserver via simple http calls.
http://docs.geoserver.org/2.0.x/en/user/extensions/rest/index.html
Not sure if it fits your needs.
-Justin
Rodolfo Barriga wrote:
you know this a really basic question ...(im just a OpenGeo user (Geoserver- gwc - OpenLayer) )
there is a way to run a process (bach script, python script, etc) to migrate the data_dir from 1.7.x to 2.0.0
i dont know something like this
python migrate.py ./1.7.7/data_dir ./2.0.0/data_dir
actually i work with 1.7.7 (with very good results :)), i create all my data_dir with python using the postgis metadata table geometry_columns ...
but i cant do this with data_dir (2.0.0) because any entity or at least styles include an id number (StyleInfoImpl--46dbec34:125896aab6e:-7fec)
... i dont know if i can create this ids number manually (i dont try yet...)
* this automated scripts helpme when i have thousands of postgis layers...
PD: sorry for my bad english
gretting
Rodolfo B.
------------------------------------------------------------------------
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
thanks you …
is a great help (i will try both) a script (with unique entities ids), and on the other hand… i will check the rest API (i dont know about that)
thanks again
Rodolfo B.
2009/12/26 Justin Deoliveira <jdeolive@anonymised.com>
Hi Rodolfo,
Unfortunately there is not really. The only way really is to start geoserver 2.0.x on the 1.7.x data directory and have it automatically generate the 2.0.x version.
That said the format is more or less straight forward so you could script it. And yes you can make up your own identifiers as long as they are of course unique, and that any references are maintained (eg layer referencing styles).
Another thing you may be interested in looking at is the rest api which allows one to configure a geoserver via simple http calls.
http://docs.geoserver.org/2.0.x/en/user/extensions/rest/index.html
Not sure if it fits your needs.
-Justin
Rodolfo Barriga wrote:
you know this a really basic question …(im just a OpenGeo user (Geoserver- gwc - OpenLayer) )
there is a way to run a process (bach script, python script, etc) to migrate the data_dir from 1.7.x to 2.0.0
i dont know something like this
python migrate.py ./1.7.7/data_dir ./2.0.0/data_dir
actually i work with 1.7.7 (with very good results :)), i create all my data_dir with python using the postgis metadata table geometry_columns …
but i cant do this with data_dir (2.0.0) because any entity or at least styles include an id number (StyleInfoImpl–46dbec34:125896aab6e:-7fec)
… i dont know if i can create this ids number manually (i dont try yet…)
- this automated scripts helpme when i have thousands of postgis layers…
PD: sorry for my bad english
gretting
Rodolfo B.
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon’s best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.