Hi,
I was trying to figure out how to get a coverage name
out of its reader looking into the old CoverageConfig
code when I stumbled into the CatalogBuilder class,
which apparently provides a similar functionality
(Eclipse "References" functinality, I love you!)...
I wish I knew about this class before, would have saved
me a few attempts at replicating the functionality in
CoverageConfig in the Wicket UI.
I also noticed nothing is using it at the moment?
Oh wait, the rest config is, and extensively, thought
it's the only user of it...
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime ha scritto:
Hi,
I was trying to figure out how to get a coverage name
out of its reader looking into the old CoverageConfig
code when I stumbled into the CatalogBuilder class,
which apparently provides a similar functionality
(Eclipse "References" functinality, I love you!)...
I wish I knew about this class before, would have saved
me a few attempts at replicating the functionality in
CoverageConfig in the Wicket UI.
I also noticed nothing is using it at the moment?
Oh wait, the rest config is, and extensively, thought
it's the only user of it...
Deh, forgot to add that the parseUOM method in both
CatalogBuilder and the old CoverageConfig class seems
broken, I guess some charset conversion issue
ruined the strings used to make conversions in the code?
Would be nice to have a coverage guy review that code.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Hi Andrea,
CatalogBuilder is my attempt to factor out a bunch of the code that used to be baked in directly to the *Info objects. And some of the stuff that the old RESTConfig classes was doing directly, that other modules could benefit from.
As you probably already noticed, the idea is to use it as a single place for all the "convenience" methods for building up catalog objects.
Apologies for not being more vocal about my work.
-Justin
Andrea Aime wrote:
Hi,
I was trying to figure out how to get a coverage name
out of its reader looking into the old CoverageConfig
code when I stumbled into the CatalogBuilder class,
which apparently provides a similar functionality
(Eclipse "References" functinality, I love you!)...
I wish I knew about this class before, would have saved
me a few attempts at replicating the functionality in
CoverageConfig in the Wicket UI.
I also noticed nothing is using it at the moment?
Oh wait, the rest config is, and extensively, thought
it's the only user of it...
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Hi Andrea,
CatalogBuilder is my attempt to factor out a bunch of the code that used to be baked in directly to the *Info objects. And some of the stuff that the old RESTConfig classes was doing directly, that other modules could benefit from.
Seems like a good approach to me.
As you probably already noticed, the idea is to use it as a single place for all the "convenience" methods for building up catalog objects.
Yep, and it works for me as well.
My mail was more along the lines of "let other people know this class is
there" since it's useful indeed.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.