This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re[2]: document() missing the document


TBP> Sounds like you need a try/except clause to bracket the call to
TBP> selectSingleNode().  javascript these days can do that.

Sorry for not having been clear. I seek a mechanism to ignore the error
in XSLT. I am aware of the JavaScript exception mechanism, but by the
time I catch that exception the transformation has failed already. I
would like to see the *transformation* succeed (with no data copied in
from zorro.xml).

In my case, zorro.xml is used to add user-defined, optional,
supplementary data to the HTML output. I am now thinking of making the
presence of zorro.xml a requirement. That's acceptable because it could
be almost empty, but it's ugly because (a) its a kludge and (b) doesn't
handle the fact that the file might be present but the connection might
be broken.

XSLT is designed to have a lot to do with distributed, networked
applications. Given that, I find language support for partial failure
shockingly poor.

Thoughts, anybody?
Bernd


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]