Looking at 1.7.x it looks like the following extensions still need to be ported to trunk:
feature-pregeneralized
imagemosaic-jdbc
geosearch
sqlserver
feature-pregen and imagemosaic-jdbc fall under Christian. I am not sure what the effort is involved in forward porting them. And I believe Christian is still out on holidays.
geosearch should be easy to port now that the rest stuff is all good to go on trunk. David, any chance you will have some time for this coming up?
sqlserver should also be easy and this one falls under me.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Mon, 2009-07-27 at 13:44 -0400, Justin Deoliveira wrote:
geosearch should be easy to port now that the rest stuff is all good
to
go on trunk. David, any chance you will have some time for this coming
up?
Yes, I can take care of this. It looks like I'll be able to take care
of this before the August 3rd RC.
--
David Winslow
OpenGeo - http://opengeo.org/
David Winslow wrote:
On Mon, 2009-07-27 at 13:44 -0400, Justin Deoliveira wrote:
geosearch should be easy to port now that the rest stuff is all good
to go on trunk. David, any chance you will have some time for this coming
up?
Yes, I can take care of this. It looks like I'll be able to take care
of this before the August 3rd RC.
Cool, i created some jira issues for these tasks:
http://jira.codehaus.org/browse/GEOS-3297
Justin
--
David Winslow
OpenGeo - http://opengeo.org/
------------------------------------------------------------------------------
_______________________________________________
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.
On Mon, 2009-07-27 at 14:42 -0400, Justin Deoliveira wrote:
David Winslow wrote:
> On Mon, 2009-07-27 at 13:44 -0400, Justin Deoliveira wrote:
>> geosearch should be easy to port now that the rest stuff is all good
>> to
>> go on trunk. David, any chance you will have some time for this coming
>> up?
>
> Yes, I can take care of this. It looks like I'll be able to take care
> of this before the August 3rd RC.
Cool, i created some jira issues for these tasks:
http://jira.codehaus.org/browse/GEOS-3297
Justin
> --
> David Winslow
> OpenGeo - http://opengeo.org/
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
So, I got this mostly ported and committed (no failing tests, so
shouldn't cause problems for anyone AFAIK). There are a couple of
inconsistencies in the catalog API that I'd like to bring up, both
embodied by modifications I had to make in the tests for the module:
1) FeatureTypeInfo.getName() no longer returns a qualified name
2) FeatureTypeInfo.getSRS().toString() now includes the EPSG: prefix.
1) Seems like an issue already discussed in discussion about a change I
recently made in the caps doc generation code
2) is probably a non-issue, but I wanted to bring them up since they
were somewhat unexpected.
If these change, I'd like a heads-up so I can update the geosearch
tests.
Thanks.
--
David Winslow
OpenGeo - http://opengeo.org/
Cool, thanks David.
So, I got this mostly ported and committed (no failing tests, so
shouldn't cause problems for anyone AFAIK). There are a couple of
inconsistencies in the catalog API that I'd like to bring up, both
embodied by modifications I had to make in the tests for the module:
1) FeatureTypeInfo.getName() no longer returns a qualified name
Yeah, FeatureTypeInfo.getPRefixedName() now does get getName() used to.
2) FeatureTypeInfo.getSRS().toString() now includes the EPSG: prefix.
Ran up against this one myself actually. And yeah, it was generally agreed that the SRS should include the prefix, although the legacy configurations stored it without.
1) Seems like an issue already discussed in discussion about a change I
recently made in the caps doc generation code
2) is probably a non-issue, but I wanted to bring them up since they
were somewhat unexpected.
If these change, I'd like a heads-up so I can update the geosearch
tests.
Thanks.
--
David Winslow
OpenGeo - http://opengeo.org/
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
All right, I've updated geosearch to use these methods. Barring some
hand-testing (which hopefully I'll get to later this week) I think it's
ready to go. However, it occurs to me that there is still the geosearch
configuration panel in the Wicket WMS module. Are there any objections
to moving that panel into the geosearch module instead? (technically a
change to core functionality)
--
David Winslow
OpenGeo - http://opengeo.org/
None here, actually prefer it. I just love to see that nice pluggable UI in action 
David Winslow wrote:
All right, I've updated geosearch to use these methods. Barring some
hand-testing (which hopefully I'll get to later this week) I think it's
ready to go. However, it occurs to me that there is still the geosearch
configuration panel in the Wicket WMS module. Are there any objections
to moving that panel into the geosearch module instead? (technically a
change to core functionality)
--
David Winslow
OpenGeo - http://opengeo.org/
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Hi Christian,
Based on commit logs and email traffic I assume you are back from vacation? Would you be able to comment on porting the feature-pregen and imagemosaic-jdbc extensions to trunk?
Thanks,
-Justin
Justin Deoliveira wrote:
Looking at 1.7.x it looks like the following extensions still need to be ported to trunk:
feature-pregeneralized
imagemosaic-jdbc
geosearch
sqlserver
feature-pregen and imagemosaic-jdbc fall under Christian. I am not sure what the effort is involved in forward porting them. And I believe Christian is still out on holidays.
geosearch should be easy to port now that the rest stuff is all good to go on trunk. David, any chance you will have some time for this coming up?
sqlserver should also be easy and this one falls under me.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Yep, I am active again, warm up is over.
I can try to port the 2 extensions (imagemosiac-jdbc should work exactly like jdbc-db2, feature-pregen has an addational geoserver specific jar file).
But until know, I never succeeded in adding an extension perfectly :-(. Remember the imagemosiac-jdbc.zip download which did not include the the jar file or the broken link to the feature-gen zip file.
Should I try ?
Justin Deoliveira writes:
Hi Christian,
Based on commit logs and email traffic I assume you are back from vacation? Would you be able to comment on porting the feature-pregen and imagemosaic-jdbc extensions to trunk?
Thanks,
-Justin
Justin Deoliveira wrote:
Looking at 1.7.x it looks like the following extensions still need to be ported to trunk:
feature-pregeneralized
imagemosaic-jdbc
geosearch
sqlserver
feature-pregen and imagemosaic-jdbc fall under Christian. I am not sure what the effort is involved in forward porting them. And I believe Christian is still out on holidays.
geosearch should be easy to port now that the rest stuff is all good to go on trunk. David, any chance you will have some time for this coming up?
sqlserver should also be easy and this one falls under me.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Hi Christian,
Christian Müller wrote:
Yep, I am active again, warm up is over.
Hope you enjoyed yourself
I can try to port the 2 extensions (imagemosiac-jdbc should work exactly like jdbc-db2, feature-pregen has an addational geoserver specific jar file).
But until know, I never succeeded in adding an extension perfectly :-(. Remember the imagemosiac-jdbc.zip download which did not include the the jar file or the broken link to the feature-gen zip file.
Well I am happy to actually do the move. I just more want to know if there is any code that needs to be updated.
Anyways, if you want to take a shot at moving them over, and i will go through to double check that everything is in order after. Sound good?
Should I try ?
Justin Deoliveira writes:
Hi Christian,
Based on commit logs and email traffic I assume you are back from vacation? Would you be able to comment on porting the feature-pregen and imagemosaic-jdbc extensions to trunk?
Thanks,
-Justin
Justin Deoliveira wrote:
Looking at 1.7.x it looks like the following extensions still need to be ported to trunk:
feature-pregeneralized
imagemosaic-jdbc
geosearch
sqlserver
feature-pregen and imagemosaic-jdbc fall under Christian. I am not sure what the effort is involved in forward porting them. And I believe Christian is still out on holidays.
geosearch should be easy to port now that the rest stuff is all good to go on trunk. David, any chance you will have some time for this coming up?
sqlserver should also be easy and this one falls under me.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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.
Afaik there is nothing to be updated. The imagemosic-jdbc.jar is completely in the geotools-2.6.x trunk, the feature-pregen has only 2 classes in geoserver, one of them deprecated.
I would propose that you make the move, that is surely faster and without the risk of errors, afterwards i will update the sphinx documentation.
This should be the fastest track
Justin Deoliveira writes:
Hi Christian,
Christian Müller wrote:
Yep, I am active again, warm up is over.
Hope you enjoyed yourself
I can try to port the 2 extensions (imagemosiac-jdbc should work exactly like jdbc-db2, feature-pregen has an addational geoserver specific jar file).
But until know, I never succeeded in adding an extension perfectly :-(. Remember the imagemosiac-jdbc.zip download which did not include the the jar file or the broken link to the feature-gen zip file.
Well I am happy to actually do the move. I just more want to know if there is any code that needs to be updated.
Anyways, if you want to take a shot at moving them over, and i will go through to double check that everything is in order after. Sound good?
Should I try ?
Justin Deoliveira writes:
Hi Christian,
Based on commit logs and email traffic I assume you are back from vacation? Would you be able to comment on porting the feature-pregen and imagemosaic-jdbc extensions to trunk?
Thanks,
-Justin
Justin Deoliveira wrote:
Looking at 1.7.x it looks like the following extensions still need to be ported to trunk:
feature-pregeneralized
imagemosaic-jdbc
geosearch
sqlserver
feature-pregen and imagemosaic-jdbc fall under Christian. I am not sure what the effort is involved in forward porting them. And I believe Christian is still out on holidays.
geosearch should be easy to port now that the rest stuff is all good to go on trunk. David, any chance you will have some time for this coming up?
sqlserver should also be easy and this one falls under me.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------- -----
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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.
Cool, deal
Christian Müller wrote:
Afaik there is nothing to be updated. The imagemosic-jdbc.jar is completely in the geotools-2.6.x trunk, the feature-pregen has only 2 classes in geoserver, one of them deprecated.
I would propose that you make the move, that is surely faster and without the risk of errors, afterwards i will update the sphinx documentation.
This should be the fastest track
Justin Deoliveira writes:
Hi Christian,
Christian Müller wrote:
Yep, I am active again, warm up is over.
Hope you enjoyed yourself
I can try to port the 2 extensions (imagemosiac-jdbc should work exactly like jdbc-db2, feature-pregen has an addational geoserver specific jar file). But until know, I never succeeded in adding an extension perfectly :-(. Remember the imagemosiac-jdbc.zip download which did not include the the jar file or the broken link to the feature-gen zip file.
Well I am happy to actually do the move. I just more want to know if there is any code that needs to be updated.
Anyways, if you want to take a shot at moving them over, and i will go through to double check that everything is in order after. Sound good?
Should I try ?
Justin Deoliveira writes:
Hi Christian, Based on commit logs and email traffic I assume you are back from vacation? Would you be able to comment on porting the feature-pregen and imagemosaic-jdbc extensions to trunk? Thanks, -Justin Justin Deoliveira wrote:
Looking at 1.7.x it looks like the following extensions still need to be ported to trunk: feature-pregeneralized
imagemosaic-jdbc
geosearch
sqlserver feature-pregen and imagemosaic-jdbc fall under Christian. I am not sure what the effort is involved in forward porting them. And I believe Christian is still out on holidays. geosearch should be easy to port now that the rest stuff is all good to go on trunk. David, any chance you will have some time for this coming up? sqlserver should also be easy and this one falls under me. -Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------- -----
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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.
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.