Hi,
I was thinking about how to start distributing the
new datastores (oracle-ng in particular) along with
GeoServer.
What about starting the distribution along with GeoServer
1.7.x series, as extension datastores, and in parallel with
the old ones, so that people interested in testing out
the latest and the greatest can start using them?
This way we would get some early feedback and fix things
so that we can do a full switch by 2.0, where only the
NG ones would be offered?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Hi Andrea,
Funny, I was just about to send a similar email :). +1 here. Basically all that needs to be done is:
1. Add extension modules for each ng datastore (there is already one there for sql server)
2. Update / Add any extension artifact descriptors (eg release/ext-oracleng.xml)
Also +1 for continuing to distribute the old for now and switch to the new for 2.0.
-Justin
Andrea Aime wrote:
Hi,
I was thinking about how to start distributing the
new datastores (oracle-ng in particular) along with
GeoServer.
What about starting the distribution along with GeoServer
1.7.x series, as extension datastores, and in parallel with
the old ones, so that people interested in testing out
the latest and the greatest can start using them?
This way we would get some early feedback and fix things
so that we can do a full switch by 2.0, where only the
NG ones would be offered?
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
not sure if this is a formal vote, but +1 from me too.
Ideally the documentation could be updated, and the UI for configuring
the old datastores should provide a convenient alternative link to UI
for the new one.
How hard would it be to apply the old store config to the new one?
Rob A
On Mon, Nov 17, 2008 at 6:23 AM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Hi Andrea,
Funny, I was just about to send a similar email :). +1 here. Basically
all that needs to be done is:
1. Add extension modules for each ng datastore (there is already one
there for sql server)
2. Update / Add any extension artifact descriptors (eg
release/ext-oracleng.xml)
Also +1 for continuing to distribute the old for now and switch to the
new for 2.0.
-Justin
Andrea Aime wrote:
Hi,
I was thinking about how to start distributing the
new datastores (oracle-ng in particular) along with
GeoServer.
What about starting the distribution along with GeoServer
1.7.x series, as extension datastores, and in parallel with
the old ones, so that people interested in testing out
the latest and the greatest can start using them?
This way we would get some early feedback and fix things
so that we can do a full switch by 2.0, where only the
NG ones would be offered?
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Hi Rob,
Rob Atkinson wrote:
not sure if this is a formal vote, but +1 from me too.
Ideally the documentation could be updated, and the UI for configuring
the old datastores should provide a convenient alternative link to UI
for the new one.
+1, good idea. I think we should add a new page for each "ng" datastore under:
http://geoserver.org/display/GEOSDOC/2.3+DataStores+configuration+details
And on each page have instructions on how to migrate from the old datastore.
How hard would it be to apply the old store config to the new one?
This is a good question. Currently the new datastores use slightly different names for parameters (uppercasing the first letter). However Andrea I think was going to change that. Is that true Andrea?
SO if we change the parameters so that they are the same then actually no change to configuration is necessary I believe since the "ng" datastores declare the same "dbtype" parameter. Is this also true Andrea?
On Mon, Nov 17, 2008 at 6:23 AM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Hi Andrea,
Funny, I was just about to send a similar email :). +1 here. Basically
all that needs to be done is:
1. Add extension modules for each ng datastore (there is already one
there for sql server)
2. Update / Add any extension artifact descriptors (eg
release/ext-oracleng.xml)
Also +1 for continuing to distribute the old for now and switch to the
new for 2.0.
-Justin
Andrea Aime wrote:
Hi,
I was thinking about how to start distributing the
new datastores (oracle-ng in particular) along with
GeoServer.
What about starting the distribution along with GeoServer
1.7.x series, as extension datastores, and in parallel with
the old ones, so that people interested in testing out
the latest and the greatest can start using them?
This way we would get some early feedback and fix things
so that we can do a full switch by 2.0, where only the
NG ones would be offered?
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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 ha scritto:
Hi Rob,
Rob Atkinson wrote:
not sure if this is a formal vote, but +1 from me too.
Ideally the documentation could be updated, and the UI for configuring
the old datastores should provide a convenient alternative link to UI
for the new one.
+1, good idea. I think we should add a new page for each "ng" datastore under:
http://geoserver.org/display/GEOSDOC/2.3+DataStores+configuration+details
And on each page have instructions on how to migrate from the old datastore.
How hard would it be to apply the old store config to the new one?
This is a good question. Currently the new datastores use slightly different names for parameters (uppercasing the first letter). However Andrea I think was going to change that. Is that true Andrea?
The idea was to make the new datastore comply with the GeoServer parameter conventions. Yet, I would like to avoid making them drop
in replacements, a user may legitimately want to have the two running
in paraller for a comparison (I know I did that a lot).
Nothing prevents one to deploy two GeoServer instances and do
the comparison like that thought... not sure which is the best one.
For me it's surely annoying since I cannot have the two running in
parallel from the IDE, but I am one, and the users are many.
SO if we change the parameters so that they are the same then actually no change to configuration is necessary I believe since the "ng" datastores declare the same "dbtype" parameter. Is this also true Andrea?
No they do not for the above reason, for example the old Oracle datastore uses "Oracle", the new one "Oracle-NG" (but you don't actually
see the dbtype param name in the UI).
Atm they also miss a lot of the previous datastore params (connection pool control) but that is easily fixed.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.