On Tue, 28 May 2002 13:27, Adam Murdoch wrote: > > > > I think I will add it in now - but what do you think - good idea or > > > > bad idea? > > > > > > Seems like a good idea. See how it goes. > > > > Turned out not to be so good. The question became which TaskContext do > > you use? > > You'd use the context for the execution frame that the listener is being > added to. Which in the case of adding listeners from the command-line, > would be the root execution frame (which the embeddor maintains).
that could work I guess. > > No matter which "scope" you used it never seemed to make sense. Not > > sure how we get configuration data from command line to TaskListener. I > > am reluctent to use setters as most listeners will not be able to be > > configured by a limited number of parameters. > > Running the listeners through a configurer might be the best bet. This > would handle listeners added from the command-line, from a config file, and > from a task, all using the same config mechanism. So some of the commandline options get translated into attributes of ModelElement and a generic entry point may also be added. You could also load config from file or whatever - I like ! -- Cheers, Peter Donald -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
