Just did a quick smoke test of transitioning from the wfs module to wfs-ng. Here is the report.
First I added a normal WFS datastore pointing to an external geoserver. This actually didn’t work all that well to be honest, I wasn’t able to preview the layer in the map preview, got errors around the FastBBOX filter.
Then I took the old wfs store off my classpath and added wfs-ng to it. This resulted in some compile errors because the WFSDataStoreFactory is not in the same package namespace. We might want to move it so that it matches exactly… I guess it depends on whether we want the two modules to co-exist on the classpath or not. Anwyays, the compile errors were trivial, after importing the data store factory from the right package everything compiled without any other work, looks liek Niels did a good job of matching the parameter names.
Fired GeoServer back up and everything worked great. For this test it actually worked much better than the old wfs since I was able to actually preview it.
That’s indeed great news. I initially just saw the part about “This actually didn’t work all that well” and my heart sank for a second. Phew!
I’ll do another test merge of Niels’ branch and my work as soon as I get a chance - but currently I’m involved with other stuff so It’ll take a while. I’ll report back and we can check that we’re still on the path of getting the Stored Query work into 2.6.
One thing I’d like to clarify: Andrea said in the meeting that feature freeze is in August, but the meeting log says in just over a month. Is feature freeze in July or August?
Btw. If anyone is at Aalborg for the INSPIRE conference, I’ll see you guys there!
Just did a quick smoke test of transitioning from the wfs module to wfs-ng. Here is the report.
First I added a normal WFS datastore pointing to an external geoserver. This actually didn’t work all that well to be honest, I wasn’t able to preview the layer in the map preview, got errors around the FastBBOX filter.
Then I took the old wfs store off my classpath and added wfs-ng to it. This resulted in some compile errors because the WFSDataStoreFactory is not in the same package namespace. We might want to move it so that it matches exactly… I guess it depends on whether we want the two modules to co-exist on the classpath or not. Anwyays, the compile errors were trivial, after importing the data store factory from the right package everything compiled without any other work, looks liek Niels did a good job of matching the parameter names.
Fired GeoServer back up and everything worked great. For this test it actually worked much better than the old wfs since I was able to actually preview it.
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems
This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate, or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.
On Wed, Jun 11, 2014 at 7:57 AM, Sampo Savolainen <
sampo.savolainen@anonymised.com> wrote:
Hi Justin,
That's indeed great news. I initially just saw the part about "This
actually didn't work all that well" and my heart sank for a second. Phew!
I'll do another test merge of Niels' branch and my work as soon as I get
a chance - but currently I'm involved with other stuff so It'll take a
while. I'll report back and we can check that we're still on the path of
getting the Stored Query work into 2.6.
One thing I'd like to clarify: Andrea said in the meeting that feature
freeze is in August, but the meeting log says in just over a month. Is
feature freeze in July or August?
Feature freeze July 18th, creation of the new 2.6.x branch and development
series unfreeze (for work scheduled to 2.7.x) August 18th while the 2.6.x
series goes RC,
2.6.0 release in September, 2.6.1 I believe in November
Cheers
Andrea
--
GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information.
Ing. Andrea Aime @geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems
That’s indeed great news. I initially just saw the part about “This actually didn’t work all that well” and my heart sank for a second. Phew!
I’ll do another test merge of Niels’ branch and my work as soon as I get a chance - but currently I’m involved with other stuff so It’ll take a while. I’ll report back and we can check that we’re still on the path of getting the Stored Query work into 2.6.
One thing I’d like to clarify: Andrea said in the meeting that feature freeze is in August, but the meeting log says in just over a month. Is feature freeze in July or August?
Feature freeze July 18th, creation of the new 2.6.x branch and development series unfreeze (for work scheduled to 2.7.x) August 18th while the 2.6.x series goes RC,
2.6.0 release in September, 2.6.1 I believe in November
Cheers
Andrea
–
==
GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
Except that is not exactly our release schedule, it's the old description
of it (previous to the last GSIP)
Hopefully Justin will pull the right one out of http://rancor.boundlessgeo.com:8080/ (currently down)
I think we were hoping to move the release date forward a couple weeks to
match up with foss4g.
Yup
Cheers
Andrea
--
GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information.
Ing. Andrea Aime @geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
Except that is not exactly our release schedule, it's the old description
of it (previous to the last GSIP)
Hopefully Justin will pull the right one out of http://rancor.boundlessgeo.com:8080/ (currently down)
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Cool, i am on it, Unless anyone objects I would like to have the wiki
attached to the geoserver wik be the one we use. So I was going to also
port the content from the geoserver.github.io wiki there as well.
Cheers
Andrea
--
GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information.
Ing. Andrea Aime @geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
Cool, i am on it, Unless anyone objects I would like to have the wiki attached to the geoserver wik be the one we use. So I was going to also port the content from the geoserver.github.io wiki there as well.
Cool, i am on it, Unless anyone objects I would like to have the wiki attached to the geoserver wik be the one we use. So I was going to also port the content from the geoserver.github.io wiki there as well.
And how often do folks that aren’t developers edit the wiki? My impression is not often. I am thinking it is not often enough to justify going against the norm.
Cool, i am on it, Unless anyone objects I would like to have the wiki attached to the geoserver wik be the one we use. So I was going to also port the content from the geoserver.github.io wiki there as well.
And how often do folks that aren’t developers edit the wiki? My impression is not often. I am thinking it is not often enough to justify going against the norm.
Cool, i am on it, Unless anyone objects I would like to have the wiki attached to the geoserver wik be the one we use. So I was going to also port the content from the geoserver.github.io wiki there as well.
