[Geoserver-devel] [Geoserver-users] Problem with QGis and WFS-T

Sorry, meant to post this reply on Devel instead of Users

···

On 3 March 2015 at 13:58, Kevin Smith <ksmith@anonymised.com> wrote:

At the moment I’m thinking a reasonable solution would be to start by just adding ‘localhost’ to the list of reflexive hostnames. That will fix the common failure case on Windows.

To handle other cases, when making a request for an external featureType, we could remember it, and then watch for WFS requests coming in with that hostname. If that happens, add the hostname to the list of self referential hostnames, roll back (maybe return a special error message?) then start on the internal path.

Allowing the admin to manually control the list of self referential hostnames might also be an idea.

On 3 March 2015 at 13:45, Izabella Mancini <izabellamancini0789@anonymised.com> wrote:

Hello Jody, Maxx and Andrea,

thank you very much for your thoroughly investigation concerning this QGIS - GeoServer WFS-T issue.
I have trouble with GeoServer WFS-T and QGIS too.
Even though I can edit (move) an existing geometry of an imported WFS-T and save my changes in QGIS. But I cannot save changes of feature attributes in QGIS for existing geometries. I can add new geometries for GeoServer WFS-T in QGIS and save them. But when I add new geometries for any GeoServer WFS-T in QGIS and try to add feature attributes too, the attributes are apparently saved without an error in QGIS but attributes are not saved in the PostgreSQL/PostGIS database. When I close QGIS the changes and adding of attributes get lost.

I use a common GeoServer 2.5.1 installation with tomcat7 7.0.52-1ubuntu0.1, Apache 2.4.7-1ubuntu4.1 running on Ubuntu 14.04 LTS. QGIS vers. is 2.8.1.

Thank you very much for your support.

Izabella


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

On 3 March 2015 at 21:16, Jody Garnett <jody.garnett@anonymised.com> wrote:

As per other email, please add your experience to http://jira.codehaus.org/browse/GEOS-6059 .

Some quick fixes:

  • If you are on windows ensure that your hosts file is configured correctly (for any tests involving localhost)
  • If you are hiding behind a proxy be sure to adjust the base url setting

The common thread here is that GeoServer needs to be able to “detect” when Transaction request document references a schema defined by DescribeFeatureType. It needs to be sure to resolve that “internally” rather than via HTTP.


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Jody Garnett

On 3 March 2015 at 03:35, emmexx <emmexx@anonymised.com> wrote:

Il 02/23/2015 08:11 AM, Andrea Aime scrisse:

A suggestion: take a recent standard GeoServer release (one downloaded
from geoserver.org <http://geoserver.org>),
repeat the test, if it fails, enable the request logging in web.xml,
and then open a ticket with all the details to reproduce, like a sample of
your data, the request that fails, and so on

I made some experiment to find out what is the problem using qgis and geoserver. The behaviour is erratic so I need some help to understand what to check.

1st experiment:
I used the aws elastic beanstalk service to install geoserver 2.6.2.
In Qgis I loaded the Tasmania road layer and I could insert new features, update geometries and attributes. The problem is that qgis always reports errors committing but sometimes data are saved, sometimes not, sometimes features are lost.
For example last week I made many test updates and usually got a qgis error but data were saved almost always.
Today I can’t update anything. I get a qgis error when I commit and data are not saved (I tried 10 times changing one attribute o adding nodes, moving lines).
Ok, this can be a qgis problem.

2nd experiment
I tried to get free of the boundless version of geoserver.
I created a new aws ami instance, installed tomcat7 and the war version of geoserver 2.6.2.
Again in qgis I added the Tasmania road layer, moved a node of a line, committed, get a qgis empty response error and from now on WFS stops responding. I have to restart tomcat in order to use again wfs.
I used the Demo requests tool and I get no answer when making wfs requests.
So this is not a qgis problem.

The default error log reports nothing.

I attach the geoserver log after select the development one.
The following are the operations I did in qgis that are reported in the log:

  • connect to geoserver
  • add the Tasmania Layer
  • move a node and change the type attribute value
  • commit (I get a qgis error)
  • remove the layer from qgis
  • add the layer: I get an error message and the layer is not added
  • I open the geoserver web Demo Requests page
  • select WFS_getFeatureBBOX-1.0.xml
  • submit (the popup open with the text Loading… and stays there)

If I can give other info or make other tests, just ask me.

Thank you
maxx


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

Want to start a new thread from the technical side of things on geoserver-devel?

···

On 3 March 2015 at 14:26, Kevin Smith <ksmith@anonymised.com> wrote:

Sorry, meant to post this reply on Devel instead of Users


Jody Garnett

On 3 March 2015 at 13:58, Kevin Smith <ksmith@anonymised.com> wrote:

At the moment I’m thinking a reasonable solution would be to start by just adding ‘localhost’ to the list of reflexive hostnames. That will fix the common failure case on Windows.

To handle other cases, when making a request for an external featureType, we could remember it, and then watch for WFS requests coming in with that hostname. If that happens, add the hostname to the list of self referential hostnames, roll back (maybe return a special error message?) then start on the internal path.

Allowing the admin to manually control the list of self referential hostnames might also be an idea.

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

On 3 March 2015 at 13:45, Izabella Mancini <izabellamancini0789@anonymised.com> wrote:

Hello Jody, Maxx and Andrea,

thank you very much for your thoroughly investigation concerning this QGIS - GeoServer WFS-T issue.
I have trouble with GeoServer WFS-T and QGIS too.
Even though I can edit (move) an existing geometry of an imported WFS-T and save my changes in QGIS. But I cannot save changes of feature attributes in QGIS for existing geometries. I can add new geometries for GeoServer WFS-T in QGIS and save them. But when I add new geometries for any GeoServer WFS-T in QGIS and try to add feature attributes too, the attributes are apparently saved without an error in QGIS but attributes are not saved in the PostgreSQL/PostGIS database. When I close QGIS the changes and adding of attributes get lost.

I use a common GeoServer 2.5.1 installation with tomcat7 7.0.52-1ubuntu0.1, Apache 2.4.7-1ubuntu4.1 running on Ubuntu 14.04 LTS. QGIS vers. is 2.8.1.

Thank you very much for your support.

Izabella


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

On 3 March 2015 at 21:16, Jody Garnett <jody.garnett@anonymised.com> wrote:

As per other email, please add your experience to http://jira.codehaus.org/browse/GEOS-6059 .

Some quick fixes:

  • If you are on windows ensure that your hosts file is configured correctly (for any tests involving localhost)
  • If you are hiding behind a proxy be sure to adjust the base url setting

The common thread here is that GeoServer needs to be able to “detect” when Transaction request document references a schema defined by DescribeFeatureType. It needs to be sure to resolve that “internally” rather than via HTTP.


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Jody Garnett

On 3 March 2015 at 03:35, emmexx <emmexx@anonymised.com> wrote:

Il 02/23/2015 08:11 AM, Andrea Aime scrisse:

A suggestion: take a recent standard GeoServer release (one downloaded
from geoserver.org <http://geoserver.org>),
repeat the test, if it fails, enable the request logging in web.xml,
and then open a ticket with all the details to reproduce, like a sample of
your data, the request that fails, and so on

I made some experiment to find out what is the problem using qgis and geoserver. The behaviour is erratic so I need some help to understand what to check.

1st experiment:
I used the aws elastic beanstalk service to install geoserver 2.6.2.
In Qgis I loaded the Tasmania road layer and I could insert new features, update geometries and attributes. The problem is that qgis always reports errors committing but sometimes data are saved, sometimes not, sometimes features are lost.
For example last week I made many test updates and usually got a qgis error but data were saved almost always.
Today I can’t update anything. I get a qgis error when I commit and data are not saved (I tried 10 times changing one attribute o adding nodes, moving lines).
Ok, this can be a qgis problem.

2nd experiment
I tried to get free of the boundless version of geoserver.
I created a new aws ami instance, installed tomcat7 and the war version of geoserver 2.6.2.
Again in qgis I added the Tasmania road layer, moved a node of a line, committed, get a qgis empty response error and from now on WFS stops responding. I have to restart tomcat in order to use again wfs.
I used the Demo requests tool and I get no answer when making wfs requests.
So this is not a qgis problem.

The default error log reports nothing.

I attach the geoserver log after select the development one.
The following are the operations I did in qgis that are reported in the log:

  • connect to geoserver
  • add the Tasmania Layer
  • move a node and change the type attribute value
  • commit (I get a qgis error)
  • remove the layer from qgis
  • add the layer: I get an error message and the layer is not added
  • I open the geoserver web Demo Requests page
  • select WFS_getFeatureBBOX-1.0.xml
  • submit (the popup open with the text Loading… and stays there)

If I can give other info or make other tests, just ask me.

Thank you
maxx


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

I changed the CC to devel with my last message. I can start a new thread instead if that’s preferable.

···

On 3 March 2015 at 14:28, Jody Garnett <jody.garnett@anonymised.com> wrote:

Want to start a new thread from the technical side of things on geoserver-devel?


Jody Garnett

On 3 March 2015 at 14:26, Kevin Smith <ksmith@anonymised.com> wrote:

Sorry, meant to post this reply on Devel instead of Users

On 3 March 2015 at 13:58, Kevin Smith <ksmith@anonymised.com> wrote:

At the moment I’m thinking a reasonable solution would be to start by just adding ‘localhost’ to the list of reflexive hostnames. That will fix the common failure case on Windows.

To handle other cases, when making a request for an external featureType, we could remember it, and then watch for WFS requests coming in with that hostname. If that happens, add the hostname to the list of self referential hostnames, roll back (maybe return a special error message?) then start on the internal path.

Allowing the admin to manually control the list of self referential hostnames might also be an idea.

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

On 3 March 2015 at 13:45, Izabella Mancini <izabellamancini0789@anonymised.com> wrote:

Hello Jody, Maxx and Andrea,

thank you very much for your thoroughly investigation concerning this QGIS - GeoServer WFS-T issue.
I have trouble with GeoServer WFS-T and QGIS too.
Even though I can edit (move) an existing geometry of an imported WFS-T and save my changes in QGIS. But I cannot save changes of feature attributes in QGIS for existing geometries. I can add new geometries for GeoServer WFS-T in QGIS and save them. But when I add new geometries for any GeoServer WFS-T in QGIS and try to add feature attributes too, the attributes are apparently saved without an error in QGIS but attributes are not saved in the PostgreSQL/PostGIS database. When I close QGIS the changes and adding of attributes get lost.

I use a common GeoServer 2.5.1 installation with tomcat7 7.0.52-1ubuntu0.1, Apache 2.4.7-1ubuntu4.1 running on Ubuntu 14.04 LTS. QGIS vers. is 2.8.1.

Thank you very much for your support.

Izabella


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

On 3 March 2015 at 21:16, Jody Garnett <jody.garnett@anonymised.com> wrote:

As per other email, please add your experience to http://jira.codehaus.org/browse/GEOS-6059 .

Some quick fixes:

  • If you are on windows ensure that your hosts file is configured correctly (for any tests involving localhost)
  • If you are hiding behind a proxy be sure to adjust the base url setting

The common thread here is that GeoServer needs to be able to “detect” when Transaction request document references a schema defined by DescribeFeatureType. It needs to be sure to resolve that “internally” rather than via HTTP.


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Jody Garnett

On 3 March 2015 at 03:35, emmexx <emmexx@anonymised.com> wrote:

Il 02/23/2015 08:11 AM, Andrea Aime scrisse:

A suggestion: take a recent standard GeoServer release (one downloaded
from geoserver.org <http://geoserver.org>),
repeat the test, if it fails, enable the request logging in web.xml,
and then open a ticket with all the details to reproduce, like a sample of
your data, the request that fails, and so on

I made some experiment to find out what is the problem using qgis and geoserver. The behaviour is erratic so I need some help to understand what to check.

1st experiment:
I used the aws elastic beanstalk service to install geoserver 2.6.2.
In Qgis I loaded the Tasmania road layer and I could insert new features, update geometries and attributes. The problem is that qgis always reports errors committing but sometimes data are saved, sometimes not, sometimes features are lost.
For example last week I made many test updates and usually got a qgis error but data were saved almost always.
Today I can’t update anything. I get a qgis error when I commit and data are not saved (I tried 10 times changing one attribute o adding nodes, moving lines).
Ok, this can be a qgis problem.

2nd experiment
I tried to get free of the boundless version of geoserver.
I created a new aws ami instance, installed tomcat7 and the war version of geoserver 2.6.2.
Again in qgis I added the Tasmania road layer, moved a node of a line, committed, get a qgis empty response error and from now on WFS stops responding. I have to restart tomcat in order to use again wfs.
I used the Demo requests tool and I get no answer when making wfs requests.
So this is not a qgis problem.

The default error log reports nothing.

I attach the geoserver log after select the development one.
The following are the operations I did in qgis that are reported in the log:

  • connect to geoserver
  • add the Tasmania Layer
  • move a node and change the type attribute value
  • commit (I get a qgis error)
  • remove the layer from qgis
  • add the layer: I get an error message and the layer is not added
  • I open the geoserver web Demo Requests page
  • select WFS_getFeatureBBOX-1.0.xml
  • submit (the popup open with the text Loading… and stays there)

If I can give other info or make other tests, just ask me.

Thank you
maxx


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

The “detect reflexive schema locations and handle them” bit is done by org.geoserver.wfs.xml.WFSURIHandler

The regular HTTP schema resolution is done by org.geotools.xml.impl.HTTPURIHandler

Both implement org.eclipse.emf.ecore.resource.URIHandler

The deadlock occurs in org.geotools.xml.Schemas.parse(String, ResourceSet) when it synchronizes on org.geotools.xml.Schemas and then tries to load the schema. This happens through several EMF objects which ultimately call URIHandler.canHandle(URI) and URIHandler.createInputStream(URI, Map<?, ?>) on a list of handlers stopping when it finds one that works.

The HTTPURIHandler’s request should time out but this doesn’t seem to be resolving the issue.

···

On 3 March 2015 at 16:34, Kevin Smith <ksmith@anonymised.com> wrote:

I changed the CC to devel with my last message. I can start a new thread instead if that’s preferable.

On 3 March 2015 at 14:28, Jody Garnett <jody.garnett@anonymised.com> wrote:

Want to start a new thread from the technical side of things on geoserver-devel?

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/


Jody Garnett

On 3 March 2015 at 14:26, Kevin Smith <ksmith@anonymised.com> wrote:

Sorry, meant to post this reply on Devel instead of Users

On 3 March 2015 at 13:58, Kevin Smith <ksmith@anonymised.com> wrote:

At the moment I’m thinking a reasonable solution would be to start by just adding ‘localhost’ to the list of reflexive hostnames. That will fix the common failure case on Windows.

To handle other cases, when making a request for an external featureType, we could remember it, and then watch for WFS requests coming in with that hostname. If that happens, add the hostname to the list of self referential hostnames, roll back (maybe return a special error message?) then start on the internal path.

Allowing the admin to manually control the list of self referential hostnames might also be an idea.

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

On 3 March 2015 at 13:45, Izabella Mancini <izabellamancini0789@anonymised.com> wrote:

Hello Jody, Maxx and Andrea,

thank you very much for your thoroughly investigation concerning this QGIS - GeoServer WFS-T issue.
I have trouble with GeoServer WFS-T and QGIS too.
Even though I can edit (move) an existing geometry of an imported WFS-T and save my changes in QGIS. But I cannot save changes of feature attributes in QGIS for existing geometries. I can add new geometries for GeoServer WFS-T in QGIS and save them. But when I add new geometries for any GeoServer WFS-T in QGIS and try to add feature attributes too, the attributes are apparently saved without an error in QGIS but attributes are not saved in the PostgreSQL/PostGIS database. When I close QGIS the changes and adding of attributes get lost.

I use a common GeoServer 2.5.1 installation with tomcat7 7.0.52-1ubuntu0.1, Apache 2.4.7-1ubuntu4.1 running on Ubuntu 14.04 LTS. QGIS vers. is 2.8.1.

Thank you very much for your support.

Izabella


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

On 3 March 2015 at 21:16, Jody Garnett <jody.garnett@anonymised.com> wrote:

As per other email, please add your experience to http://jira.codehaus.org/browse/GEOS-6059 .

Some quick fixes:

  • If you are on windows ensure that your hosts file is configured correctly (for any tests involving localhost)
  • If you are hiding behind a proxy be sure to adjust the base url setting

The common thread here is that GeoServer needs to be able to “detect” when Transaction request document references a schema defined by DescribeFeatureType. It needs to be sure to resolve that “internally” rather than via HTTP.


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Jody Garnett

On 3 March 2015 at 03:35, emmexx <emmexx@anonymised.com> wrote:

Il 02/23/2015 08:11 AM, Andrea Aime scrisse:

A suggestion: take a recent standard GeoServer release (one downloaded
from geoserver.org <http://geoserver.org>),
repeat the test, if it fails, enable the request logging in web.xml,
and then open a ticket with all the details to reproduce, like a sample of
your data, the request that fails, and so on

I made some experiment to find out what is the problem using qgis and geoserver. The behaviour is erratic so I need some help to understand what to check.

1st experiment:
I used the aws elastic beanstalk service to install geoserver 2.6.2.
In Qgis I loaded the Tasmania road layer and I could insert new features, update geometries and attributes. The problem is that qgis always reports errors committing but sometimes data are saved, sometimes not, sometimes features are lost.
For example last week I made many test updates and usually got a qgis error but data were saved almost always.
Today I can’t update anything. I get a qgis error when I commit and data are not saved (I tried 10 times changing one attribute o adding nodes, moving lines).
Ok, this can be a qgis problem.

2nd experiment
I tried to get free of the boundless version of geoserver.
I created a new aws ami instance, installed tomcat7 and the war version of geoserver 2.6.2.
Again in qgis I added the Tasmania road layer, moved a node of a line, committed, get a qgis empty response error and from now on WFS stops responding. I have to restart tomcat in order to use again wfs.
I used the Demo requests tool and I get no answer when making wfs requests.
So this is not a qgis problem.

The default error log reports nothing.

I attach the geoserver log after select the development one.
The following are the operations I did in qgis that are reported in the log:

  • connect to geoserver
  • add the Tasmania Layer
  • move a node and change the type attribute value
  • commit (I get a qgis error)
  • remove the layer from qgis
  • add the layer: I get an error message and the layer is not added
  • I open the geoserver web Demo Requests page
  • select WFS_getFeatureBBOX-1.0.xml
  • submit (the popup open with the text Loading… and stays there)

If I can give other info or make other tests, just ask me.

Thank you
maxx


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/