On Mon, 14 Jan 2002 00:35, Paulo Gaspar wrote: > > It most cases Context will be sub-classed for a particular domain. For > > instance in phoenix there is BlockContext while in ant there is > > TaskContext. > > Both subclass Context to supply domain specific interaction. You could do > > that in your framework ;) > > Then the ServiceManager and the ComponentManager could as well be > implemented by subclassing a Context and they could be considered > Contexts to!!!
And if you have fixed smallish services provided to all components then the CM should not be used and they should be merged into Context. > (Same stretching logic.) Not a stretch :) Both TaskContext and BlockContext have methods that could be put into services but because they are small bits of functionality common to most of their component they are available via the Context. Consider TaskContext.resolveFile(String) - this functionality could be pushed into a new FileResolverService and thus exposed via CM but it was a deliberate choice to merge it into the Context. -- Cheers, Pete ------------------------------------------------------------ militant agnostic: i don't know, and you don't know either. ------------------------------------------------------------ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
