在介绍依赖项与安全的章节中，你可以更直观地看到用 `raise` 异常代替 `return` 值的优势。

本例中，客户端用不存在的 `ID` 请求 `item` 时，触发状态码为 `404` 的异常：

{* ../../docs_src/handling_errors/tutorial001_py310.py hl[11] *}

### 响应结果 { #the-resulting-response }

请求为 `http://example.com/items/foo`（`item_id` 为 `"foo"`）时，客户端会接收到 HTTP 状态码 200 及如下 JSON 响应结果：

```JSON
{
  "item": "The Foo Wrestlers"
}
```

    }

    /**
     * Converts an SmbException to an IOException.
     *
     * @param se the SmbException to convert
     * @return the resulting IOException
     */
    protected IOException seToIoe(final SmbException se) {
        IOException ioe = se;
        Throwable root = se.getRootCause();
        if (root instanceof TransportException) {

У цьому прикладі, коли клієнт запитує елемент за ID, якого не існує, згенеруйте виключення з кодом статусу `404`:

{* ../../docs_src/handling_errors/tutorial001_py310.py hl[11] *}

### Отримана відповідь { #the-resulting-response }

Якщо клієнт робить запит за шляхом `http://example.com/items/foo` (де `item_id` `"foo"`), він отримає код статусу HTTP 200 і JSON відповідь:

```JSON
{
  "item": "The Foo Wrestlers"
}
```

Bu örnekte, client var olmayan bir ID ile bir item istediğinde, `404` status code’u ile bir exception raise edelim:

{* ../../docs_src/handling_errors/tutorial001_py310.py hl[11] *}

### Ortaya Çıkan Response { #the-resulting-response }

Client `http://example.com/items/foo` (bir `item_id` `"foo"`) isterse, HTTP status code olarak 200 ve şu JSON response’u alır:

```JSON
{
  "item": "The Foo Wrestlers"
}
```

            if (channel.getErrorRate() > 0.1) {
                log.warn("High error rate on channel {}: {}", 
                    channel.getChannelId(), channel.getErrorRate());
                // Consider removing channel
            }
        }
    }
    
    private void discoverInterfaces() {
        if (!multiChannelEnabled) return;
        

 * equals</i>. That is, {@code a.compareTo(b)} or {@code comparator.compare(a, b)} should equal zero
 * <i>if and only if</i> {@code a.equals(b)}. If this advice is not followed, the resulting
 * collection will not correctly obey its specification.
 *
 * <p>See the Guava User Guide article on <a href=
 * "https://github.com/google/guava/wiki/ImmutableCollectionsExplained">immutable collections</a>.
 *

{* ../../docs_src/handling_errors/tutorial001_py310.py hl[11] *}

### El response resultante { #the-resulting-response }

Si el cliente solicita `http://example.com/items/foo` (un `item_id` `"foo"`), ese cliente recibirá un código de estado HTTP de 200, y un response JSON de:

```JSON
{
  "item": "The Foo Wrestlers"
}

Neste exemplo, quando o cliente pede, na requisição, por um item cujo ID não existe, a exceção com o status code `404` é lançada:

{* ../../docs_src/handling_errors/tutorial001_py310.py hl[11] *}

### A response resultante { #the-resulting-response }

Se o cliente faz uma requisição para `http://example.com/items/foo` (um `item_id` `"foo"`), esse cliente receberá um HTTP status code 200, e uma resposta JSON:


```JSON
{
  "item": "The Foo Wrestlers"

        return false;
      }

      Entry<?, ?> entry = (Entry<?, ?>) object;
      inverse.delegate.remove(entry.getValue());
      /*
       * Remove the mapping in inverse before removing from esDelegate because
       * if entry is part of esDelegate, entry might be invalidated after the
       * mapping is removed from esDelegate.
       */
      esDelegate.remove(entry);
      return true;
    }

 * </ul>
 *
 * <h3>Format Preservation</h3>
 * <ul>
 *   <li><strong>Whitespace Preservation</strong>: Maintains original formatting when removing elements</li>
 *   <li><strong>Comment Preservation</strong>: Preserves XML comments and processing instructions</li>
 *   <li><strong>Line Separator Handling</strong>: Uses system-appropriate line separators</li>
 * </ul>