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.
So, in the end you need for each component that you can use in different situations a ComponentSelector. Hmm, I have to think about this. Thanks for your reply, Carsten > > > > what do you think of extending the > > org.apache.excalibur.xml.sax.Parser interface by > > adding a parse() method: > > > > void parse( InputSource in, > > ContentHandler contentHandler, > > LexicalHandler lexicalHandler, > > Parameters parameters ) > > throws SAXException, IOException; > > > > With this method you can influence the parsing, e.g. > > turn on/off validation for this parse cycle etc. > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
