So, you can keep raising **FastAPI**'s `HTTPException` as normally in your code.

But when you register an exception handler, you should register it for Starlette's `HTTPException`.

This way, if any part of Starlette's internal code, or a Starlette extension or plug-in, raises a Starlette `HTTPException`, your handler will be able to catch and handle it.

        // Default constructor
    }

    /**
     * Initializes the facet query view with default file type queries.
     * This method is called after dependency injection to set up file type facets
     * and register all queries with the FacetInfo component.
     */
    @PostConstruct
    public void init() {
        final String filetypeField = ComponentUtil.getFessConfig().getIndexFieldFiletype();

            dependsOn("signGradleDistributionPublication")
        }
    }
}

/**
 * Tasks that are called by the (currently separate) promotion build running on CI.
 */
tasks.register("promotionBuild") {
    description = "Build production distros, smoke test them and publish"
    group = "publishing"
    dependsOn(":packageBuild", "publish")

import org.apache.maven.plugin.LegacySupport;
import org.apache.maven.project.ProjectBuilder;

/**
 * This realizes the metadata source via the default hint to provide backward-compat with Maven 2.x whose Plexus version
 * registered component descriptors twice: once keyed by role+roleHint and once keyed by role only. This effectively
 * made the metadata source available with its original role hint ("maven") as well as the default hint.
 *
 */
@Named

 * Java ServiceLoader mechanism, allowing plugins and extensions to contribute functionality
 * to the Maven build process.
 * <p>
 * SPI services are typically registered in {@code META-INF/services/} files corresponding to
 * the specific service interface being implemented.
 * <p>
 * All SPI services should be annotated with {@link Consumer} to indicate they are meant to be

Para hacer eso, y para acomodar diferentes necesidades de aplicaciones, hay varias formas en que puede hacerlo. Algunas formas populares son:

* **Modificar algunos registros DNS**.
    * Para esto, el programa de renovación necesita soportar las API del proveedor de DNS, por lo que, dependiendo del proveedor de DNS que estés utilizando, esto podría o no ser una opción.

    "crossVersionTests": false
  },
  {
    "name": "service-registry-builder",
    "path": "platforms/core-runtime/service-registry-builder",
    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "service-registry-impl",
    "path": "platforms/core-runtime/service-registry-impl",
    "unitTests": true,
    "functionalTests": false,

   *
   * @return the source of this event.
   */
  public Object getSource() {
    return source;
  }

  /**
   * Returns the wrapped, 'dead' event, which the system was unable to deliver to any registered
   * subscriber.
   *
   * @return the 'dead' event that could not be delivered.
   */
  public Object getEvent() {
    return event;
  }

  @Override
  public String toString() {

  // 'main'. Work around this by creating a 'main' source set that forwards to 'jvmMain'.
  //
  // The forwarding SourceSet also needs to fake out some task names to prevent them from being
  // registered twice.
  //
  // https://github.com/bndtools/bnd/issues/6590
  val jvmMainSourceSet = sourceSets.getByName("jvmMain")
  val mainSourceSet =
    object : SourceSet by jvmMainSourceSet {

	quarkus/extensions/jsonp/runtime/pom.xml
quarkus/extensions/schema-registry/confluent/avro/deployment/pom.xml
	quarkus/extensions/schema-registry/confluent/avro/runtime/pom.xml
	quarkus/extensions/avro/deployment/pom.xml
	quarkus/extensions/schema-registry/confluent/common/deployment/pom.xml
	quarkus/extensions/schema-registry/devservice/deployment/pom.xml
quarkus/extensions/kubernetes/kind/deployment/pom.xml