Jeff, > So my questions to the "Xerces team" would: > 1) How come you have not implemented such interface since it is part of SAX2 > ( assuming that has not been done)? Any technical reasons?
Since SAX2 implementation was introduced before my time, I am not quite sure why this was missed. By looking at its API, I guess there is no technical reason why it couldn't be implemented ... > 2) There was a code submission to this a few months ago, why it didn't make > it into the Xerces-c codebase? any problems with it or just not enough time I think it was just missed since it is not reported in Bugzilla. It is recommended to log any patch or bug in Bugzilla to avoid getting lost in the mailing list. I have just reviewed his patch, looks ok, but one more thing to consider is how to create such XMLFilter. Should we provide a factory method (like XMLReaderFactory::createXMLReader()) or let user to new XMLFilterImpl directly? Memory management is something to think about. > ( I could volunteer to reviewed and check it in if I still > have committer access ). Although theoretically a committer for one sub-project automatically got permission to access other projects, it is not recommended to abuse such rights. As each subproject can be quite different, it's better to get involved with the sub-project and the mailing list first, submit patch and got reputation before assuming the committer status. Even Xerces-J and Xerces-C++ are very close, they are still two quite different projects. But volunteer effort to review or submit patch is very welcome and appreciated. Just my two cents. Thanks! Tinny ----- Original Message ----- From: "Jeffrey Rodriguez" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 27, 2002 1:34 PM Subject: SAX2 XMLFilter interface some questions > Was looking over Xerces-c source and couldn't find XMLFilter interface > implementation. > I read a message around March where somebody posted source for a XMLFilter > interface implementation. > I want to be able to intercept and process SAX content events as a consumer > of events and then in turn being able to process the events and act as a > producer of events on a pipeline. > I know that I could probably do this through advance handlers but I think > that a more consistent way of doing this is through an implementaion of > XMLFilter. > So my questions to the "Xerces team" would: > 1) How come you have not implemented such interface since it is part of SAX2 > ( assuming that has not been done)? Any technical reasons? > 2) There was a code submission to this a few months ago, why it didn't make > it into the Xerces-c codebase? any problems with it or just not enough time > ( I could volunteer to reviewed and check it in if I still > have committer access ). > Thanks, > Jeffrey Rodriguez > > > > > > _________________________________________________________________ > Add photos to your messages with MSN 8. Get 2 months FREE*. > http://join.msn.com/?page=features/featuredemail > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
