RE: [Geoserver-devel] Ingestion Engine

GeoServer GeoServer Developer
1

Hi Alessio,
what do you mean exactly by "...ingestion engine"
and by "...At the end the user should be able
to manage Geoserver data like a file system directory tree"???
I'm asking this because it sounds like something we may need too,
but maybe I'm misunderstanding...

Regarding Quartz, I'm not a guru about licences, but I think there should be
no problem. GeoServer uses the GPL, so if you develop a new
piece of software that "links" to it, or that cannot exists without it,
that new piece of software must be under the GPL too.
But it's not true the other way around. The licence of Quartz lets you
use it for whatever purpose, even within commercial products, and that
surely doesn't exclude GPL products.

Maybe it's true that if GeoServer won't work anymore without Quartz,
that could be a "contamination" of the GPL, I don't know...

Looking, very briefly, on the Net I found these links:
http://java-source.net/open-source/job-schedulers

Bye
Paolo Rizzi

-----Original Message-----
From: Alessio Fabiani
To: geoserver-devel@lists.sourceforge.net
Sent: 15/07/2005 11.54
Subject: [Geoserver-devel] Ingestion Engine

Hi list,
I'm going to implement an ingestion engine for Geoserver data because
trying to use the actual ingestion system with a large amount of data
is near impossible.

Me and Simone have discussed a lot about it, and finally we have
decided to build something similar to the "Live Deploy" in Tomcat or
JBoss, basically a thread that at certain temporal intervals reads the
file system and checks for changes. At the end the user should be able
to manage Geoserver data like a file system directory tree.

I would like to start building the main thread and I'm evaluating
several solutions. It would be great to use Quartz Scheduler but I
think that it has a License incompatible with the Geoserver one.

Does someone know if there is any other open source scheduler
available on the net?

Any suggestion about this idea will be very appreciated.

Cheers,
                Alessio.

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

2

Hi Paolo,
thank you for your interest.

On 7/15/05, P. Rizzi Ag.Mobilità Ambiente <paolo.rizzi@anonymised.com> wrote:

Hi Alessio,
what do you mean exactly by "...ingestion engine"
and by "...At the end the user should be able
to manage Geoserver data like a file system directory tree"???
I'm asking this because it sounds like something we may need too,
but maybe I'm misunderstanding...

We'd like to avoid as much as possible using the GeoServer web
interface for data management both for features and coverages in order
to ease administrator's job. We'd like to allow GeoServer to
automatically recognize the type of the files uploaded onto the data
directory and to dispatch them to the right service.
Moreover, once the administrator deletes a file or a subdir from data,
GeoServer should be able to remove automatically the feature/coverage
from the services.

Another open issue related to this one would be having the possibility
to handle nested wms layers reflecting an hypothetical file system
defined or user-defined structure, but at this moment we have no
suggestion on this topic.

We would like to hear something on these topics from the other active
GeoServer developers (david, chris, etc..) since we are talking about
major changes/improvements and everybody's opinion is very very
welcome.

Regarding Quartz, I'm not a guru about licences, but I think there should be
no problem. GeoServer uses the GPL, so if you develop a new
piece of software that "links" to it, or that cannot exists without it,
that new piece of software must be under the GPL too.
But it's not true the other way around. The licence of Quartz lets you
use it for whatever purpose, even within commercial products, and that
surely doesn't exclude GPL products.

I don't think that Quartz scheduler license is compatible with GPL 2.0
because it uses a private license compatible with the Apache one,
that, as far as I know, is not compatible with GPL 2.0 (maybe I'm
wrong ... I don't know exactly).

Maybe it's true that if GeoServer won't work anymore without Quartz,
that could be a "contamination" of the GPL, I don't know...

Looking, very briefly, on the Net I found these links:
http://java-source.net/open-source/job-schedulers

Bye
Paolo Rizzi

P.S.: any help will be greatly appreciated :slight_smile:

Ciao.

-----Original Message-----
From: Alessio Fabiani
To: geoserver-devel@lists.sourceforge.net
Sent: 15/07/2005 11.54
Subject: [Geoserver-devel] Ingestion Engine

Hi list,
I'm going to implement an ingestion engine for Geoserver data because
trying to use the actual ingestion system with a large amount of data
is near impossible.

Me and Simone have discussed a lot about it, and finally we have
decided to build something similar to the "Live Deploy" in Tomcat or
JBoss, basically a thread that at certain temporal intervals reads the
file system and checks for changes. At the end the user should be able
to manage Geoserver data like a file system directory tree.

I would like to start building the main thread and I'm evaluating
several solutions. It would be great to use Quartz Scheduler but I
think that it has a License incompatible with the Geoserver one.

Does someone know if there is any other open source scheduler
available on the net?

Any suggestion about this idea will be very appreciated.

Cheers,
               Alessio.

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

3

Hi Paolo,
thank you for your interest.

On 7/15/05, P. Rizzi Ag.Mobilità Ambiente <paolo.rizzi@anonymised.com> wrote:

Hi Alessio,
what do you mean exactly by "...ingestion engine"
and by "...At the end the user should be able
to manage Geoserver data like a file system directory tree"???
I'm asking this because it sounds like something we may need too,
but maybe I'm misunderstanding...

We'd like to avoid as much as possible using the GeoServer web
interface for data management both for features and coverages in order
to ease administrator's job. We'd like to allow GeoServer to
automatically recognize the type of the files uploaded onto the data
directory and to dispatch them to the right service.
Moreover, once the administrator deletes a file or a subdir from data,
GeoServer should be able to remove automatically the feature/coverage
from the services.

Another open issue related to this one would be having the possibility
to handle nested wms layers reflecting an hypothetical file system
defined or user-defined structure, but at this moment we have no
suggestion on this topic.

We would like to hear something on these topics from the other active
GeoServer developers (david, chris, etc..) since we are talking about
major changes/improvements and everybody's opinion is very very
welcome.

Regarding Quartz, I'm not a guru about licences, but I think there should be
no problem. GeoServer uses the GPL, so if you develop a new
piece of software that "links" to it, or that cannot exists without it,
that new piece of software must be under the GPL too.
But it's not true the other way around. The licence of Quartz lets you
use it for whatever purpose, even within commercial products, and that
surely doesn't exclude GPL products.

I don't think that Quartz scheduler license is compatible with GPL 2.0
because it uses a private license compatible with the Apache one,
that, as far as I know, is not compatible with GPL 2.0 (maybe I'm
wrong ... I don't know exactly).

Maybe it's true that if GeoServer won't work anymore without Quartz,
that could be a "contamination" of the GPL, I don't know...

Looking, very briefly, on the Net I found these links:
http://java-source.net/open-source/job-schedulers

Bye
Paolo Rizzi

P.S.: any help will be greatly appreciated :slight_smile:

Ciao.

4

Regarding Quartz, I'm not a guru about licences, but I think there
should be
no problem. GeoServer uses the GPL, so if you develop a new
piece of software that "links" to it, or that cannot exists without
it,
that new piece of software must be under the GPL too.
But it's not true the other way around. The licence of Quartz lets
you
use it for whatever purpose, even within commercial products, and
that
surely doesn't exclude GPL products.

Looking more closely, it looks like the current quartz is gpl
incompatible, since it's bsd style, which says you have to include
credit, which the gpl doesn't allow. But it says the upcoming version
1.5 is going to be Apache 2.0, which gets into muddy terriritory with
GPL incompatibility - it was designed to be gpl compatible, but didn't
_quite_ make it: http://www.apache.org/licenses/GPL-compatibility.html
I'd so go ahead and use it if it is the best solution, and if push
comes to shove we can make it a separate module or some such. The plan
is to eventually re-architect geoserver to be a lot more plug-in based,
perhaps even with an lgpl or less core, and then the key components
would be GPL - this component could then be Apache licensed or whatnot.

The ingestion engine sounds good, I need to understand it a bit more,
but if two of our biggest users both have the need then I can probably
be convinced pretty easily. And indeed others have asked for similar
functionality in the past. Just code with an eye towards keeping it
separate and pluggable at a later date. Perhaps we should even have a
GeoServer specific meeting at some point, talk about feature versioning
and the ingestion stuff. We also should try to get our roadmaps in
line, since we're getting a bunch of work going on in the branches, and
we need good strategies to bring it all in to trunk. We don't want the
branches diverging too far, and I think both of you want to build off
of the raster stuff, perhaps we may consider branching 1.3 in a stable
branch and getting. I need to review wcs-branch again, but one thing I
definitely want to see before it goes stable is to not differentiate
between vector and coverages when adding data. The data menu is too
cluttered, it should just be one 'data' button, where you can select
spatial dbs, files (vector or raster), ect. See
http://jira.codehaus.org/browse/GEOS-340 for my thoughts on our current
state - I think coverages should just be another option in 'data', that
then takes you straight to the layer config page.

best regards,

Chris

Maybe it's true that if GeoServer won't work anymore without Quartz,
that could be a "contamination" of the GPL, I don't know...

Looking, very briefly, on the Net I found these links:
http://java-source.net/open-source/job-schedulers

Bye
Paolo Rizzi

-----Original Message-----
From: Alessio Fabiani
To: geoserver-devel@lists.sourceforge.net
Sent: 15/07/2005 11.54
Subject: [Geoserver-devel] Ingestion Engine

Hi list,
I'm going to implement an ingestion engine for Geoserver data because
trying to use the actual ingestion system with a large amount of data
is near impossible.

Me and Simone have discussed a lot about it, and finally we have
decided to build something similar to the "Live Deploy" in Tomcat or
JBoss, basically a thread that at certain temporal intervals reads
the
file system and checks for changes. At the end the user should be
able
to manage Geoserver data like a file system directory tree.

I would like to start building the main thread and I'm evaluating
several solutions. It would be great to use Quartz Scheduler but I
think that it has a License incompatible with the Geoserver one.

Does someone know if there is any other open source scheduler
available on the net?

Any suggestion about this idea will be very appreciated.

Cheers,
                Alessio.

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration
Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration
Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/