Andy Clark wrote:
> (+) Define Filter Interfaces
Done.
This should make pipeline construction easier. Now if someone
would write a dynamic configuration or tool to generate the
code for a configuration based on an XML file (for example),
that would be super cool.
Here's a proposal for a super-simple configuration DTD:
<!ELEMENT config (property*,pipeline?)>
<!ELEMENT property EMPTY>
<!ATTLIST property id ID #REQUIRED>
<!ATTLIST property class NMTOKEN #REQUIRED>
<!ELEMENT pipeline (doc?,dtd?,dtdcm?)>
<!ELEMENT doc (scanner,filter*)>
<!ELEMENT dtd (scanner,filter*)>
<!ELEMENT dtdcm (scanner,filter*)>
<!ELEMENT scanner EMPTY>
<!ATTLIST scanner idref IDREF #REQUIRED>
<!ELEMENT filter EMPTY>
<!ATTLIST filter idref IDREF #REQUIRED>
For example, the following config file would construct a
configuration with just a scanner -- no namespace binder or
validation:
<config>
<property id='doc-scanner'
class='org.apache.xerces.impl.XMLDocumentScannerImpl'/>
<property id='dtd-scanner'
class='org.apache.xerces.impl.XMLDTDScannerImpl'/>
<pipeline>
<doc> <scanner idref='doc-scanner'/> </doc>
<dtd> <scanner idref='dtd-scanner'/> </dtd>
<dtdcm> <scanner idref='dtd-scanner'/> </dtdcm>
</pipeline>
</config>
Who wants to have some fun implementing it as a sample?
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
