# Body - Multiple Parameters { #body-multiple-parameters }

Now that we have seen how to use `Path` and `Query`, let's see more advanced uses of request body declarations.

## Mix `Path`, `Query` and body parameters { #mix-path-query-and-body-parameters }

First, of course, you can mix `Path`, `Query` and request body parameter declarations freely and **FastAPI** will know what to do.

 */
package org.codelibs.fess.crawler.util;

import java.io.IOException;
import java.io.Reader;
import java.io.StringReader;

import org.codelibs.core.lang.StringUtil;
import org.codelibs.fess.crawler.util.TextUtil.TextNormalizeContext;
import org.dbflute.utflute.core.PlainTestCase;

/**
 * @author shinsuke
 * @author kaorufuzita
 */
public class TextUtilTest extends PlainTestCase {

	<!-- The components of DBFlute Runtime. -->
	<component name="invokerAssistant" class="org.codelibs.fess.opensearch.common.ImplementedInvokerAssistant"/>
	<component name="behaviorCommandInvoker" class="org.dbflute.bhv.core.BehaviorCommandInvoker"/>

	<!-- The components of Behavior. -->
	<component name="userBhv" class="org.codelibs.fess.opensearch.user.exbhv.UserBhv"/>

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package okhttp3.internal.publicsuffix

import androidx.test.core.app.ApplicationProvider
import okhttp3.internal.platform.PlatformRegistry
import org.robolectric.RobolectricTestRunner

actual typealias PublicSuffixTestRunner = RobolectricTestRunner

actual fun beforePublicSuffixTest() {

* etc.

It can be convenient to quickly access HTTP (and WebSocket) status codes in your app, using autocompletion for the name without having to remember the integer status codes by memory.

Read more about it in the [FastAPI docs about Response Status Code](https://fastapi.tiangolo.com/tutorial/response-status-code/).

## Example

```python
from fastapi import FastAPI, status

app = FastAPI()

 *
 * <p>The reverse operation <b>may</b> be a strict <i>inverse</i> (meaning that {@code
 * converter.reverse().convert(converter.convert(a)).equals(a)} is always true). However, it is very
 * common (perhaps <i>more</i> common) for round-trip conversion to be <i>lossy</i>. Consider an
 * example round-trip using {@link com.google.common.primitives.Doubles#stringConverter}:
 *
 * <ol>

          return new FutureAsCancellable(immediateCancelledFuture());
        }
        // We reschedule ourselves with a lock held for two reasons. 1. we want to make sure that
        // cancel calls cancel on the correct future. 2. we want to make sure that the assignment
        // to currentFuture doesn't race with itself so that currentFuture is assigned in the
        // correct order.
        Throwable scheduleFailure = null;

   * <p>"In the order that they complete" means, for practical purposes, about what you would
   * expect, but there are some subtleties. First, we do guarantee that, if the output future at
   * index n is done, the output future at index n-1 is also done. (But as usual with futures, some
   * listeners for future n may complete before some for future n-1.) However, it is possible, if

 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
 * either express or implied. See the License for the specific language
 * governing permissions and limitations under the License.
 */
package org.codelibs.fess.score;

import java.util.Map;

import org.opensearch.search.rescore.RescorerBuilder;

/**
 * Interface for query rescoring implementations.
 */
public interface QueryRescorer {
    /**

 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
 * either express or implied. See the License for the specific language
 * governing permissions and limitations under the License.
 */
package org.codelibs.core.misc;

import java.util.Locale;

import junit.framework.TestCase;

/**
 * @author higa
 *
 */
public class LocaleUtilTest extends TestCase {

    /**
     * @throws Exception
     */