Hi Nuno,
Thanks for checking, I realise now that I configured datastores with a non
existing schema, in that case GeoServer can connect to the DB but cannot find
any featuretypes. So an empty list makes sense in that situation. When I
misconfigured the datastore with wrong connection details the behaviour is
indeed like you describe (with the unfortunate 404) for GeoServer 2.12.
For GeoServer 2.10 I found some weird behavioural difference between list=all
and list=available:
Invalid Oracle datastore (misconfigured port):
- featuretypes.xml?list=all RESPONSE: HTTP 200 OK, BODY: <featureTypes/>
- featuretypes.xml?list=available RESPONSE: HTTP 500 SERVER ERROR, BODY: Could
not load datastore: oracle:null
Invalid PostGIS datastore (misconfigured port):
- featuretypes.xml?list=all RESPONSE: HTTP 200 OK, BODY: <featureTypes/>
- featuretypes.xml?list=available RESPONSE: HTTP 500 SERVER ERROR, BODY: Could
not load datastore: postgis:null
In case anyone else ever runs into this.
Kind regards,
Anton
Hi,
I just made a test with two types of data store (shapefile and postgis), and
both fail with the exception (and an unfortunate 404 exception code,
it should be 500 IMHO) if the connection parameters are not correct:
Could not load datastore: <datastore_name>
Note that this will only fail if the *list=all* query parameter is provided,
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception
will be returned (which is the correct behavior).
Please double check that you are targeting a data store with invalid connection
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.
If you want to take a look at code you should look here:
I just made a test with two types of data store (shapefile and postgis), and
both fail with the exception (and an unfortunate 404 exception code,
it should be 500 IMHO) if the connection parameters are not correct:
Could not load datastore: <datastore_name>
Note that this will only fail if the *list=all* query parameter is provided,
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception
will be returned (which is the correct behavior).
Please double check that you are targeting a data store with invalid connection
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.
If you want to take a look at code you should look here:
it should be 500 IMHO) if the connection parameters are not correct:
Could not load datastore: <datastore_name>
Note that this will only fail if the *list=all* query parameter is provided,
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception
will be returned (which is the correct behavior).
Please double check that you are targeting a data store with invalid connection
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.
If you want to take a look at code you should look here:
Could not load datastore: <datastore_name>
Note that this will only fail if the *list=all* query parameter is provided,
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception
will be returned (which is the correct behavior).
Please double check that you are targeting a data store with invalid connection
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.
If you want to take a look at code you should look here:
Could not load datastore: <datastore_name>
Note that this will only fail if the *list=all* query parameter is provided,
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception
will be returned (which is the correct behavior).
Please double check that you are targeting a data store with invalid connection
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.
If you want to take a look at code you should look here:
Note that this will only fail if the *list=all* query parameter is provided,
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception
will be returned (which is the correct behavior).
Please double check that you are targeting a data store with invalid connection
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.
If you want to take a look at code you should look here:
layers for the data store will be listed and indeed in that case no exception
will be returned (which is the correct behavior).
Please double check that you are targeting a data store with invalid connection
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.
If you want to take a look at code you should look here:
Please double check that you are targeting a data store with invalid connection
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.
If you want to take a look at code you should look here:
*list=all* query parameter and that no cache is happening. If you still don't
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.
If you want to take a look at code you should look here:
to open a JIRA ticket describing the issue and how to reproduce it.
If you want to take a look at code you should look here:
If you want to take a look at code you should look here:
https://github.com/nmco/geoserver/blob/a2cb6f17455231decd4b0b4de28e9825bb8ba2cc/src/restconfig/src/main/java/org/geoserver/rest/catalog/FeatureTypeController.java#L83-L149
<https://github.com/nmco/geoserver/blob/a2cb6f17455231decd4b0b4de28e9825bb8ba2cc/src/restconfig/src/main/java/org/geoserver/rest/catalog/FeatureTypeController.java#L83-L149>
Hoper it helps,
Nuno Oliveira
On 09/27/2017 12:19 PM, Anton Bakker wrote:
> Hi all,
>
> I am trying to determine through the REST API whether the connection details
> for a given datastore is valid. In the web interface a user receives an
> error message (https://i.imgur.com/Aa61yFX.png
> <https://i.imgur.com/Aa61yFX.png>) when trying to configure a datastore with
> invalid connection details, but in the REST API I cannot find a way to
> determine whether a datastore is valid.
>
> When using the REST API GeoServer lets me create a new datastore with invalid
> connection details. When I check for the number of available featuretypes in
> the invalid datastore through the REST API, the request completes
> successfully:
>
> REQUEST:
> GET
> http://daneel:8080/geoserver/rest/workspaces/world/datastores/da00bb64-f124-4d9c-be2a-89fd94bb09df/featuretypes.xml?list=all
>
> <http://daneel:8080/geoserver/rest/workspaces/world/datastores/da00bb64-f124-4d9c-be2a-89fd94bb09df/featuretypes.xml?list=all>
> HTTP/1.1
>
> RESPONSE BODY:
> <featureTypes/>
>
> However, I would expect GeoServer to return an error since GS cannot
> determine the number of featuretypes in the datastore, since it cannot
> connect to the datastore. Can this be seen as a bug? Or is there another way
> to validate datastore configurations through the REST API?
>
> Cheers,
> Anton
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> <http://sdm.link/slashdot>
>
>
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to this
> list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> <http://www.ianturton.com/talks/foss4g.html#/>
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
> <http://geoserver.org/comm/userlist-guidelines.html>
>
> Geoserver-users@...
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
> <https://lists.sourceforge.net/lists/listinfo/geoserver-users>
--
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
<http://goo.gl/it488V> for more information.
==
Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.it <http://www.geo-solutions.it/>
http://twitter.com/geosolutions_it <http://twitter.com/geosolutions_it>
-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo
è consentito esclusivamente al destinatario del messaggio, per le finalità
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne
il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di
procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro
sistema. Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse,
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the
attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act (Legislative
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in
accord with its purpose, any disclosure, reproduction, copying, distribution,
or either dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the intended
recipient, please contact immediately the sender by telephone, fax or e-mail
and delete the information in this message that has been received in error. The
sender does not give any warranty or accept liability as the content, accuracy
or completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.
https://github.com/nmco/geoserver/blob/a2cb6f17455231decd4b0b4de28e9825bb8ba2cc/src/restconfig/src/main/java/org/geoserver/rest/catalog/FeatureTypeController.java#L83-L149
<https://github.com/nmco/geoserver/blob/a2cb6f17455231decd4b0b4de28e9825bb8ba2cc/src/restconfig/src/main/java/org/geoserver/rest/catalog/FeatureTypeController.java#L83-L149>
Hoper it helps,
Nuno Oliveira
On 09/27/2017 12:19 PM, Anton Bakker wrote:
> Hi all,
>
> I am trying to determine through the REST API whether the connection details
> for a given datastore is valid. In the web interface a user receives an
> error message (
On 09/27/2017 12:19 PM, Anton Bakker wrote:
> Hi all,
>
> I am trying to determine through the REST API whether the connection details
> for a given datastore is valid. In the web interface a user receives an
> error message (
On 09/27/2017 12:19 PM, Anton Bakker wrote:
> Hi all,
>
> I am trying to determine through the REST API whether the connection details
> for a given datastore is valid. In the web interface a user receives an
> error message (
> I am trying to determine through the REST API whether the connection details
> for a given datastore is valid. In the web interface a user receives an
> error message (
ST API whether the connection details for a given datastore is valid. In the
web interface a user receives an error message (https://i.imgur.com/Aa61yFX.png
<https://i.imgur.com/Aa61yFX.png>) when trying to configure a datastore with
invalid connection details, but in the REST API I cannot find a way to
determine whether a datastore is valid.
>
> When using the REST API GeoServer lets me create a new datastore with invalid
> connection details. When I check for the number of available featuretypes in
> the invalid datastore through the REST API, the request completes
> successfully:
>
> REQUEST:
> GET
> When using the REST API GeoServer lets me create a new datastore with invalid
> connection details. When I check for the number of available featuretypes in
> the invalid datastore through the REST API, the request completes
> successfully:
>
> REQUEST:
> GET
> GET
http://daneel:8080/geoserver/rest/workspaces/world/datastores/da00bb64-f124-4d9c-be2a-89fd94bb09df/featuretypes.xml?list=all
<http://daneel:8080/geoserver/rest/workspaces/world/datastores/da00bb64-f124-4d9c-be2a-89fd94bb09df/featuretypes.xml?list=all>
HTTP/1.1
>
> RESPONSE BODY:
> <featureTypes/>
>
> However, I would expect GeoServer to return an error since GS cannot
> determine the number of featuretypes in the datastore, since it cannot
> connect to the datastore. Can this be seen as a bug? Or is there another way
> to validate datastore configurations through the REST API?
>
> Cheers,
> Anton
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> RESPONSE BODY:
> <featureTypes/>
>
> However, I would expect GeoServer to return an error since GS cannot
> determine the number of featuretypes in the datastore, since it cannot
> connect to the datastore. Can this be seen as a bug? Or is there another way
> to validate datastore configurations through the REST API?
>
> Cheers,
> Anton
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> <featureTypes/>
>
> However, I would expect GeoServer to return an error since GS cannot
> determine the number of featuretypes in the datastore, since it cannot
> connect to the datastore. Can this be seen as a bug? Or is there another way
> to validate datastore configurations through the REST API?
>
> Cheers,
> Anton
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> However, I would expect GeoServer to return an error since GS cannot
> determine the number of featuretypes in the datastore, since it cannot
> connect to the datastore. Can this be seen as a bug? Or is there another way
> to validate datastore configurations through the REST API?
>
> Cheers,
> Anton
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> Cheers,
> Anton
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> Anton
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> <http://sdm.link/slashdot>
>
>
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to this
> list:
> - Earning your support instead of buying it, but Ian Turton:
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to this
> list:
> - Earning your support instead of buying it, but Ian Turton:
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to this
> list:
> - Earning your support instead of buying it, but Ian Turton:
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to this
> list:
> - Earning your support instead of buying it, but Ian Turton:
> Please make sure you read the following two resources before posting to this
> list:
> - Earning your support instead of buying it, but Ian Turton:
> - Earning your support instead of buying it, but Ian Turton:
ead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
<http://www.ianturton.com/talks/foss4g.html#/>
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
> <http://geoserver.org/comm/userlist-guidelines.html>
>
> Geoserver-users@...
>
>
https://lists.sourceforge.net/lists/listinfo/geoserver-users
<https://lists.sourceforge.net/lists/listinfo/geoserver-users>
--
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts! Visit
Nuno Oliveira
==
GeoServer Professional Services from the experts! Visit
==
GeoServer Professional Services from the experts! Visit
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
<http://goo.gl/it488V> for more information.
==
Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
Software Engineer
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
phone: +39 0584 962313
fax: +39 0584 1660272
fax: +39 0584 1660272
fax: +39 0584 1660272
http://www.geo-solutions.it <http://www.geo-solutions.it/>
http://twitter.com/geosolutions_it <http://twitter.com/geosolutions_it>
-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo
è consentito esclusivamente al destinatario del messaggio, per le finalità
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne
il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di
procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro
sistema. Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse,
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the
attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act (Legislative
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in
accord with its purpose, any disclosure, reproduction, copying, distribution,
or either dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the intended
recipient, please contact immediately the sender by telephone, fax or e-mail
and delete the information in this message that has been received in error. The
sender does not give any warranty or accept liability as the content, accuracy
or completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.
http://www.geo-solutions.it <http://www.geo-solutions.it/>
http://twitter.com/geosolutions_it <http://twitter.com/geosolutions_it>
-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo
è consentito esclusivamente al destinatario del messaggio, per le finalità
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne
il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di
procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro
sistema. Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse,
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the
attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act (Legislative
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in
accord with its purpose, any disclosure, reproduction, copying, distribution,
or either dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the intended
recipient, please contact immediately the sender by telephone, fax or e-mail
and delete the information in this message that has been received in error. The
sender does not give any warranty or accept liability as the content, accuracy
or completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo
è consentito esclusivamente al destinatario del messaggio, per le finalità
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne
il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di
procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro
sistema. Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse,
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the
attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act (Legislative
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in
accord with its purpose, any disclosure, reproduction, copying, distribution,
or either dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the intended
recipient, please contact immediately the sender by telephone, fax or e-mail
and delete the information in this message that has been received in error. The
sender does not give any warranty or accept liability as the content, accuracy
or completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.
The information in this message and/or attachments, is intended solely for the
attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act (Legislative
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in
accord with its purpose, any disclosure, reproduction, copying, distribution,
or either dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the intended
recipient, please contact immediately the sender by telephone, fax or e-mail
and delete the information in this message that has been received in error. The
sender does not give any warranty or accept liability as the content, accuracy
or completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.
is intended solely for the attention and use of the named addressee(s) and may
be confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data
Protection Code).Any use not in accord with its purpose, any disclosure,
reproduction, copying, distribution, or either dissemination, either whole or
partial, is strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact immediately
the sender by telephone, fax or e-mail and delete the information in this
message that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent messages
and accepts no responsibility for changes made after they were sent or for
other risks which arise as a result of e-mail transmission, viruses, etc.
ust made a test with two types of data store (shapefile and postgis), and both
fail with the exception (and an unfortunate 404 exception code,
should be 500 IMHO) if the connection parameters are not correct:
* query parameter is provided, otherwise only the configured
indeed in that case no exception will be returned (which is the correct
behavior).
a data store with invalid connection parameters and using the
he is happening. If you still don't see any exception message I will suggest you
e and how to reproduce it.
should look here:
Nuno Oliveira
> Hi all,
>
>
in the invalid datastore through the REST API, the request completes
successfully:
>
> REQUEST:
>
E BODY:
reTypes/>
>
ever, I would expect GeoServer to return an error since GS cannot determine the
number of featuretypes in the datastore, since it cannot connect to the
datastore. Can this be seen as a bug? Or is there another way to validate
datastore configurations through the REST API?
>
Cheers,
Anton
>
------------------------------------------------------------------------------
>
_______________________________________________
>
e following two resources before posting to this list:
> Geoserver-users@...
Regards,
o Oliveira
==
Oliveira
@nmcoliveira
e Engineer
lutions S.A.S.
di Montramito 3/A
54 Massarosa (LU)
aly
hone: +39 0584 962313
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente
riservate. Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate
questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
