Mircea Toma wrote: > > > Mircea Toma wrote: > > > > > > I wouldn't do that. By passing parameters to configure a > > > Component you break > > > SoC pattern. I would just have different parsers configured with > different > > > parameters and select them using the CS or CM. > > > > > Hmm, I agree partially with you here. Now, I think configuring > a component > > will all different configuration sets is not the right approach: > > You end up having a "validating parser", a "non-validation parser", > > a "validation and xyz parser", a "validation and not xyz parser" etc. > > And your application really needs all those four. > > Is it the application that needs all these parsers or one > component/service? > Actually both :) - There are areas of your application where you know that you for example should not validate - or even better, it's configurable by the user. Imagine a desktop application, like an XML editor where you can say validate or not for applying a stylesheet (something like this). Internally you use avalon and the parser component and have to get a component with the correct behaviour.
> > > > So, in the end you need for each component that you can use in > > different situations a ComponentSelector. > > > > > Phoenix has this ability of providing different component > implementations to > different components without using a selector. I guess this would > solve your > problem conceptually but if you have to use ECM than I agree using a > selector for parsers is not very nice. > Yes, that's right - As a better solution than selectors will be in the next implementations anyway, this problem will also disappear. Thanks Carsten -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
