DO NOT REPLY [Bug 10630] - Source interface does not specify source

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10630>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10630

Source interface does not specify source

keshlam@us.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Normal                      |Enhancement



------- Additional Comments From keshlam@us.ibm.com  2002-07-10 13:16 -------
Given how different the content of different kinds of Source can be, there 
really isn't a lot of common behavior among them and special-case code seems to 
be unavoidable. (Processing of a SAXSource and DOMSource run through completely 
different DTM models, to take one obvious example.)

If you want to introduce a new type of source without changing the rest of 
Xalan, it will have to follow the behavior of one of the existing varieties. 
That being the case, your simplest solution would seem to be to subclass and 
extend one of those. If you correctly emulate the behavior of the existing 
Source class, this should work with no changes to the existing Xalan code base.

I honestly don't see what else we can do here. If you have a specific proposal, 
great; please provide details!