Re: exception classes

[Suzanne Dirkers]

Hi,

        I am talking about trying to give more explicit information on what
an exception that is caught is all about, as in the SimpleXPathAPI sample,
for example, there is a try/catch block where the catch part basically
catches ANY kind of exception and it appears the most the programmer can do
is just say "Exception caught!" but it seems it would be good to be able to
say  what kind of exception, or give some kind of clue as to why a
particular API is giving back an exception. For example, if I'm getting an
exception because XPATH doesn't know what my namespace is, it would be nice
to be able to print out "Exception: unresolved namespace prefix urn:" , for
example.

Suzanne


                                                                                       
                                         
                      Joseph                                                           
                                         
                      Kesselman/Watson/        To:       [EMAIL PROTECTED]             
                                  
                      [EMAIL PROTECTED]                cc:                             
                                                 
                                               Subject:  Re: exception classes         
                                         
                      03/14/2003 10:46                                                 
                                         
                      AM                                                               
                                         
                      Please respond to                                                
                                         
                      xalan-dev                                                        
                                         
                                                                                       
                                         
                                                                                       
                                         




The XSLT language doesn't really have any concept of exceptions; it can
neither catch them nor throw them. The closest you can come is using
<xsl:message> with terminate="yes", which will produce an error and --
unless you've overridden this behavior with a custom error handler -- shut
down the XSLT processor.

If that doesn't answer your question, could you be more explicit about
what you're trying to do (or avoid)?

______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"may'ron DaroQbe'chugh vaj bIrIQbej"  ("Put down the squeezebox and nobody
gets hurt.")