In this case, you'll need to surround your code with a try catch block.
在这种情况下，需要用一个try catch程序块来包围代码。
The command bean is instantiated and a try catch block is used to catch exceptions generated from a duplicate user, an invalid credit card, or an unauthorized credit card.
命令bean被实例化，try catch块被用于捕捉由于重复的用户、无效的信用卡或未经认证的信用卡而产生的异常。
The Surround with menu lets you easily wrap lines of code you've written with try... catch, for, and while loops.
Surround With菜单使您能够轻松地将使用try…catch、for和while循环编写的代码行打包。
To use the doQuery method, you need to establish a database connection and call the method from within a try ... catch block, as shown in Listing 4.
要使用doQuery方法，需要建立数据库连接并且从try ...catch块内调用方法，如清单4 所示。
With the asyncEcho test, it wraps the asserts in a try/catch, and any errors are passed back to the DOH through the deferred.errback(error) call.
对于asyncEcho测试，它将断言包装进一个try/catch 程序块，并且，任何错误都将通过 deferred.errback(error) 调用被传递回DOH。
You should try (catch) up with the others in your class.
你应该尽力赶上班上的其他同学。
A try... catch structure changes the runtime exception behavior to what is specified in the catch clause.
catch结构将运行时异常行为更改为catch子句中所指定的行为。
To detect this bug pattern, you'll need to know where the try-catch blocks are, what might be thrown out of the try block, and what is caught in the catch blocks.
要检测此bug模式，则需要知道try -catch块的位置、try块可能抛出的内容以及在catch块中将捕获的内容。
Listing 4 shows the preceding code in a try... catch structure.
清单4展示了try…catch结构中的上述代码。
Each CodeException contains the starting and ending bytecode offset for the corresponding try block, so you can easily determine which CodeException objects correspond to a try-catch block.
每个CodeException都包含相应try块的起始和终止的字节码偏移量，这样您可以方便地确定哪一个CodeException对象与try - catch块对应。
While on the subject, it's worth noting that although the examples in this series use try-catch() blocks to trap and handle exceptions, this isn't strictly necessary.
关于这个问题，有一点值得注意：尽管本系列中的示例使用 try-catch() 代码块来捕捉和处理异常，但这并不是必须的。
These contain information about all the try-catch blocks in the method, so you'll have to correlate the throw and catch information to identify the bug pattern.
它们包含关于方法中所有try - catch块的信息，所以您必须将抛出信息和捕获信息关联，以标识bug模式。
The code should ideally be wrapped by try-catch blocks.
最好把代码放在try -catch块中。
If you need more complex behavior, you can add try-catch-finally blocks.
如果需要更复杂的行为，那么也可以添加try - catch -finally块。
When invoking unknown code (which listeners certainly qualify as), it is prudent to execute it in a try-catch block so that ill-behaved listeners do not do more damage than necessary.
在调用未知代码(侦听器就是这样的代码)时，谨慎的方式是在try - catch块中执行它，这样，行为有误的侦听器不会造成更多不必要的破坏。
If the content isn't supported, the code throws an exception, which is caught by the try-catch block.
如果内容不受支持，那么代码抛出一个异常，此异常由try - catch块捕捉到。
Because the category property can either be multivalued or single-valued, you check for it with a try-catch statement.
因为分类属性可以是多值的也可以是单值的，所以要用try - catch语句检查它。
Use TRY..CATCH construct or check the @@ERROR variable after executing a data manipulation statement (like INSERT/UPDATE/DELETE).
在执行数据操作语句（像INSERT/UPDATE/DELETE)之后，使用TRY..CATCH结构或者检查该@@ERROR变量
However, you'll still need to use the old try-catch style if you want to test the exception's detail message or other properties.
但是如果您想要测试异常的详细消息或其他属性，则仍然需要使用旧式的try - catch样式。
From the SOAP client perspective, it's a good idea to wrap the SOAP call inside a try-catch block, so that SOAP faults like the one above can be caught and handled gracefully.
对于SOAP客户端来说，将这个SOAP调用封装在一个try - catch代码块中是很好的做法，这样类似于上面的SOAP错误就会被顺利地捕捉和处理。
If you can, use a try-catch block.
如果能，那么使用try - catch块。
If the stored procedure contains a TRY... CATCH construct, the error transfers control to the CATCH block in the stored procedure.
如果存储过程包含TRY…CATCH构造，则错误会将控制传输给存储过程中的CATCH块。
If the stored procedure contains a TRY... CATCH construct, the error transfers control to the CATCH block in the stored procedure.
如果存储过程包含TRY…CATCH构造，则错误会将控制传输给存储过程中的CATCH块。
应用推荐