Neeme & Mircea,
You guys on about the same thing?
In true IoC style, the block that needs it would implement an interface like "XMLParsing" and have a method called "registerParser(..)" or something. I think the Cocoon component is just a replacement for SAX in that it has previously had something statically set in it. Rememebr that Phoenix is a multi app machine that might require several parsers active in the same VM... Err, or have I got that wrong.
Regards,
- Paul
I remember Berin mentioned the possibility for future package org.apache.avalon.excalibur.xml.parser, that would then contain the "ideal" IoC behavioral interface to XML parsing? That would allow us to plug in non-SAX- and non-JAXP-compatible parsers as well.
-----Original Message----- From: Paul Hammant [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2001 11:40 AM To: Avalon Development Subject: XML Parser availablity for Phoenix components.
OK, a Phoenix block requires XML parsing capability. Should it use the SAX factory, the JAXP replacement for that or is there an IoC ideal that we should aspire to? For calls to configure() you don't get a choice, you use the parser that phoenix is using, but for XML things completely contained inside the hosted server component, what's right?
Regards,
- Paul H
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
