[Geoserver-devel] picking up hibernate catalog

Ciao Emanuele et al,

Recently i have been given the go ahead to start helping out / working on the hibernate catalog stuff that is currently sitting in community.

As we left the work I believe Emanuele and myself agreed on a bit of refactoring the current catalog stuff into a dao interface. With basically a single catalog implementation where most of the logic sits and then the data access stuff in the dao implementations.

The question of factoring out the catalog beans into a separate module was also risen but I think was agreed that is an orthogonal proposal.

So, I want to pick up that work but I don’t want to step on anyones toes. So just thought I would run it by you guys.

Thanks.

-Justin


Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

On 09/22/2010 09:11 PM, Justin Deoliveira wrote:

Ciao Emanuele et al,

Recently i have been given the go ahead to start helping out / working
on the hibernate catalog stuff that is currently sitting in community.

Justin,

since I have a few cycles to spare and I am interested too in the hibernate catalog, I'd be happy to help.

From a quick look at the code I inferred the catalog is tightly tied to the rest of the code, hence an alternative catalog (be it Hibernate or othwerise) will not be easily maintainable, is that so ?

Actually, just to make the build work I had to add a few stubs to allow for what has been recently added to the catalog and for the evolution of the GeoServer interface (there is a wrapper to substitute an Hibernate-aware class for GeoServerImpl).

Regards,

Luca Morandini
[http://www.lucamorandini.it]

Hi Luca,

Well my first plan is to do a bit of refactoring of the code so that most/all the logic sits in the catalog itself, and the data access parts sit standalone behind a dao interface. At the moment the two are quite mixed.

So after this refactor it should be much easier to implement new dao implementations. However they will still be tied closely to the core catalog model.

There has been talk of breaking that model out standalone. But i see this as a future step.

-Justin

On Thu, Sep 23, 2010 at 3:04 AM, Luca Morandini <lmorandini@anonymised.com> wrote:

On 09/22/2010 09:11 PM, Justin Deoliveira wrote:

Ciao Emanuele et al,

Recently i have been given the go ahead to start helping out / working
on the hibernate catalog stuff that is currently sitting in community.

Justin,

since I have a few cycles to spare and I am interested too in the hibernate
catalog, I’d be happy to help.

From a quick look at the code I inferred the catalog is tightly tied to the rest
of the code, hence an alternative catalog (be it Hibernate or othwerise) will not
be easily maintainable, is that so ?

Actually, just to make the build work I had to add a few stubs to allow for what
has been recently added to the catalog and for the evolution of the GeoServer
interface (there is a wrapper to substitute an Hibernate-aware class for
GeoServerImpl).

Regards,

Luca Morandini
[http://www.lucamorandini.it]


Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev


Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel


Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.