avalon newbie: Innocent question, please don't hurt me -- servicesstrategy with Avalon framework

[Andrew C. Oliver]

Some time ago someone sent me some ideas on how to use avalon in a
service based strategy such that it would be more containment based
than inheritance based (and bare will me that I regard interface implementation as inheritance because its "is a" not "has a"). Basically, I don't want everything to implement 10 different interfaces. i'd rather null operations... So I lost the message (long story short, fired, lost laptop, rehired by same company in different group, new laptop...stupid mozilla default settings had deleted mail of my server against my will).. But I'm ready to do it now ;-)

What I basically want is:

public class AbstractService implements x, y, z, ... {

??

public SomeType someLifecycleMethodImNotUsing() {
return null;
}

}

What are the x, y, and zs that I should most likely use? And what else do I need?

In short my application is a reporting service which lets me pull from a number of data sources, execute various transformations and get out a report via various delivery methods. So I have DataProviderService which has for instance a JDBCService which can process QueryDefs to get stuff from a database (I don't ermember the names I have thus far). So far I've stubbed most things out and I'm fairly happy with it, but I'd rather not re-invent the wheel, hence my interest in using Avalon in place of the little "Service" and "ServiceManager" classes I used as placeholders..

Thoughts?

thanks,

Andy




--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>