#18 Adding extends property

[Dejan Krsmanovic]

Here is an idea:
We could add one special property to scanners or
pipeline stages configuration. That property should point
to another component (scanner or pipeline stage) and it
should mean that we want all properties from parent
component to have the same values as properties from
child component.

For example, if we have two scanners that have all
properties the same but they scans different folders and
put their scanned messages into different pipelines we
could make one scanner extend another one scanner (or
even create one abstract scanner with all common
properties). That way we could make our config files
smaller.

[Robert Fuller]

Logged In: YES
user_id=51384

In an XML configuration file you may be able to do this
already (ie., write a set of configuration properties once and
use it several times in the same file) by using external
entities.

[Dejan Krsmanovic]

Logged In: YES
user_id=608954

We should have easer and more general way of doing this, so
it could be applied on properties files too.

[Robert Fuller]

Logged In: YES
user_id=51384

How about some kind of PropertySet, which can have an id and a set
of properties, and which can be subsequently referenced from other
points in the configuration?

[Dejan Krsmanovic]

Logged In: YES
user_id=608954

OK but that is something very similiar to my original idea:
Having an property that would point on another component
and have all its configuration options set. That another
component (scanner, pipeline stage) could be abstract in
case it is something like PropertySet you suggested, or just
another (non abstract) component.

Components should be in parent-child relationship, and child
component could redefine value of some option in parent
component.

[bruce mcdonald]

Logged In: YES
user_id=547388

Good idea - lets keep it for the 1.x series. There are going to be lots of time
to do this. The build was the big thing holding up the 1.0 release.