* supplied object is the root. Expressions like 'child.name' will translate into
 * 'rootObject.getChild().getName()' for non-boolean properties, and
 * 'rootObject.getChild().isName()' for boolean properties.
 *
 * @deprecated use {@code org.apache.maven.api.services.ModelBuilder} instead
 */
@Deprecated(since = "4.0.0")
public class ObjectBasedValueSource extends AbstractValueSource {

# FastAPI and friends newsletter

<iframe data-w-type="embedded" frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="https://xr4n4.mjt.lu/wgt/xr4n4/hj5/form?c=40a44fa4" width="100%" style="height: 800px;"></iframe>

			<arg>"//AREA"</arg>
			<arg>"href"</arg>
		</postConstruct>
		<postConstruct name="put">
			<arg>"//FRAME"</arg>
			<arg>"src"</arg>
		</postConstruct>
		<postConstruct name="put">
			<arg>"//IFRAME"</arg>
			<arg>"src"</arg>
		</postConstruct>
		<postConstruct name="put">
			<arg>"//IMG"</arg>
			<arg>"src"</arg>
		</postConstruct>
		<postConstruct name="put">
			<arg>"//LINK"</arg>
			<arg>"href"</arg>

    </jsp:include>

    <main class="content-wrapper position-relative">
        <iframe class="w-100 h-100 position-absolute" style="border: 0;"
                src="<%=request.getContextPath()%>${serverPath}<%= response.encodeURL("/_plugin/kopf/") %>"
                title="<la:message key="labels.dashboard_plugin" />"></iframe>
    </main>

    <jsp:include page="/WEB-INF/view/common/admin/footer.jsp"></jsp:include>
</div>

Do you want to just have a `str`? Or just a `dict`? Or a database class model instance directly? It all works the same way.

You actually don't have users that log in to your application but robots, bots, or other systems, that have just an access token? Again, it all works the same.

        Profile p = Profile.newBuilder().activation(a).build();

        return p;
    }

    private Properties newProperties(String osName, String osVersion, String osArch) {
        Properties props = new Properties();
        props.setProperty("os.name", osName);
        props.setProperty("os.version", osVersion);
        props.setProperty("os.arch", osArch);
        return props;
    }

    @Test

   *       the same.
   *   <li>The unreserved characters ".", "-", "~", and "_" remain the same.
   *   <li>The general delimiters "@" and ":" remain the same.
   *   <li>The subdelimiters "!", "$", "&amp;", "'", "(", ")", "*", "+", ",", ";", and "=" remain
   *       the same.
   *   <li>The space character " " is converted into %20.

## Declare model attributes { #declare-model-attributes }

You can then use `Field` with model attributes:

{* ../../docs_src/body_fields/tutorial001_an_py310.py hl[11:14] *}

`Field` works the same way as `Query`, `Path` and `Body`, it has all the same parameters, etc.

/// note | Technical Details

### Testing file { #testing-file }

Then you could have a file `test_main.py` with your tests. It could live on the same Python package (the same directory with a `__init__.py` file):

``` hl_lines="5"
.
├── app
│   ├── __init__.py
│   ├── main.py
│   └── test_main.py
```

Because this file is in the same package, you can use relative imports to import the object `app` from the `main` module (`main.py`):

# Cookie Parameters { #cookie-parameters }

You can define Cookie parameters the same way you define `Query` and `Path` parameters.

## Import `Cookie` { #import-cookie }

First import `Cookie`:

{* ../../docs_src/cookie_params/tutorial001_an_py310.py hl[3] *}

## Declare `Cookie` parameters { #declare-cookie-parameters }

Then declare the cookie parameters using the same structure as with `Path` and `Query`.