# Extra Data Types { #extra-data-types }

Up to now, you have been using common data types, like:

* `int`
* `float`
* `str`
* `bool`

But you can also use more complex data types.

And you will still have the same features as seen up to now:

* Great editor support.
* Data conversion from incoming requests.
* Data conversion for response data.
* Data validation.
* Automatic annotation and documentation.

- **Flexibility and Control:**
Java serialization offers limited control over the serialization process, such as excluding certain fields, customizing naming conventions, and handling complex data structures more gracefully.

- **Security:**
Java serialization poses security risks, especially related to deserialization vulnerabilities.

- **Version Compatibility:**

legal counsel or licensing specialists to audit and ensure your application is in compliance with the licenses of MinIO and all other open-source projects with which your application integrates or interacts. We understand that AGPLv3 licensing is complex and nuanced. It is for that reason we strongly encourage using experts in licensing to make any such determinations around compliance instead of relying on apocryphal or anecdotal advice.

[MinIO Commercial Licensing](https://min.io/pricing)...

* Validate **complex structures**:
    * Use of hierarchical Pydantic models, Python `typing`’s `List` and `Dict`, etc.
    * And validators allow complex data schemas to be clearly and easily defined, checked and documented as JSON Schema.

        assertTrue(auth.matches("ftp://192.168.1.1/test/aaa.html"));
        assertFalse(auth.matches("ftp://hostname/test/aaa.html"));

        // Test with more complex paths
        auth.setServer("hostname");
        auth.setPort(21);
        assertTrue(auth.matches("ftp://hostname:21/path/to/resource.txt"));
        assertTrue(auth.matches("ftp://hostname/path/to/resource.txt"));

real(complexT) floatT
imag(complexT) floatT
</pre>

<p>
The type of the arguments and return value correspond.
For <code>complex</code>, the two arguments must be of the same
<a href="#Numeric_types">floating-point type</a> and the return type is the
<a href="#Numeric_types">complex type</a>
with the corresponding floating-point constituents:

        NtlmHttpURLConnection spiedConnection = spy(ntlmConnection);
        doNothing().when(spiedConnection).connect();
        // Mock the handshake process to do nothing complex
        mockResponse(HTTP_OK, "OK", null, null);

        // Act & Assert
        assertDoesNotThrow(() -> spiedConnection.getResponseCode());
        // Use reflection to verify handshake method is called

        assertNotNull(builder);

        DefaultModelBuildingRequest request = new DefaultModelBuildingRequest();
        request.setProcessPlugins(true);
        request.setPomFile(getPom("complex"));
        request.setSystemProperties(sysProperties);

        ModelBuildingResult result = builder.build(request);
        assertNotNull(result);
        assertNotNull(result.getEffectiveModel());

 * <p>
 * This annotation can be used on static methods to programmatically create and configure
 * beans that will be managed by the dependency injection container. It's particularly
 * useful when the bean creation requires complex logic or when the bean needs to be
 * configured based on runtime conditions.
 * <p>
 * Example usage:
 * <pre>
 * public class Providers {
 *     {@literal @}Provides
 *     {@literal @}Singleton

        }
    }

    @Nested
    class AttributeAndStateTests {

        @Test
        public void testGetTypeForFile() throws Exception {
            // Mocking underlying connection and info retrieval is complex.
            // This test focuses on the logic based on the URL structure.
            SmbFile file = new SmbFile("smb1://server/share/file.txt");
            // Without a real connection, getType relies on path parsing.