Hi all,
looking into http://jira.codehaus.org/browse/GEOS-2352
I noticed that all the old xml reading/writing code is
still around. Since we're not using it anymore, isn't
it a good time to remove them?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
(+1)^2
I know it is still +1 but it shows much more support than just +1.
Simone.
On Tue, Nov 11, 2008 at 11:20 AM, Andrea Aime <aaime@anonymised.com> wrote:
Hi all,
looking into http://jira.codehaus.org/browse/GEOS-2352
I noticed that all the old xml reading/writing code is
still around. Since we're not using it anymore, isn't
it a good time to remove them?Cheers
Andrea--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.-------------------------------------------------------------------------
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
--
-------------------------------------------------------
Eng. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
mob: +39 333 8128928
http://www.geo-solutions.it
http://www.geo-solutions.it/simone.giannecchini
http://www.linkedin.com/in/simonegiannecchini
-------------------------------------------------------
Well we still use the writer, just the reader has been replaced. The rationale being to create the new catalog/config objects on the read phase and ensure that our persistence stays the same on the write phase.
Another note, i have found having the old reader around useful when trying to diagnose bugs with the new one... might be good to keep it around for a little while... i would also be fine with putting it some legacy package or something.
Andrea Aime wrote:
Hi all,
looking into http://jira.codehaus.org/browse/GEOS-2352
I noticed that all the old xml reading/writing code is
still around. Since we're not using it anymore, isn't
it a good time to remove them?Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
that makes a (-1)^2 so 
just an idea, if you still want it to perform diagnosis, wouldn't that mean to
move it to the tests source folder and use it to check the correctness of the
new one by an alternate, well proven method?
2c.
Gabriel
On Tuesday 11 November 2008 02:43:15 pm Justin Deoliveira wrote:
Well we still use the writer, just the reader has been replaced. The
rationale being to create the new catalog/config objects on the read
phase and ensure that our persistence stays the same on the write phase.Another note, i have found having the old reader around useful when
trying to diagnose bugs with the new one... might be good to keep it
around for a little while... i would also be fine with putting it some
legacy package or something.Andrea Aime wrote:
> Hi all,
> looking into http://jira.codehaus.org/browse/GEOS-2352
> I noticed that all the old xml reading/writing code is
> still around. Since we're not using it anymore, isn't
> it a good time to remove them?
>
> Cheers
> Andrea