RE: returning IXMLDOMNodeList node-set in msxml

Hmm on closer consideration the whole matter had best be dropped, if I
use addObject for the solution it will have unintended consequences on
media portability, i.e the media which are generated once such as PDF
will work fine, but dynamically generated media such as a webpage would
need some restructuring. 

i.e I can have the dynamic file mydynamic.xex as a resource of
programmable.xml in the single-generation media because the application
knows at generation time what files are resources of programmable.xml
but at the web media the application does not keep track of what
resources an individual document has, this is left to the discretion of
the xslt.
I don't necessarily think that it is an error in logic to have this
split in processing models, the split seems to occur naturally the model
has been chosen which is best suited to a particular media.

Thus the rule will have to be that xex files can not be resources of
another document, but can only be top-level documents. Not a big
problem.


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list