Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I need to know, whether extjs 3.1 is available of exception handling and logging build in library .
Like Logging the exception as log file , with the specification of error whether it is major or minor or critical or info.
new log file creating on specified size exceeded. etc…
There’s nothing like that built in. AFAIK, this is not something you’ll find in many (any?) JS-based frameworks. Exception handling and logging take a lot of code to do framework-wide (not to mention the added performance overhead), so you’d never want to build that in without some way of extracting it back out for a production build. While possible in theory, this would basically involve writing or extending an existing JS parser that could do so, which would be no small feat.
Re: exception handling, there is some in the framework where it makes sense, but really in any development framework, runtime errors usually bubble up by design. There is often not a good default way to handle an exception (as opposed to an end application which can choose to display the error to the user in some meaningful way). More importantly, since the end user of a framework is you, the developer, you’ll want to know immediately about any runtime exceptions in your code (or even in the framework itself for that matter).
Logging is definitely possible (and useful) but you’ll have to roll your own as needed.