Helidon MP+MongoDB Pokemon示例抛出Mapper异常求助

Hey there, let's break down this issue you're facing. You've got a Pokemon POC running on Helidon MP with MongoDB DBClient, where fetching data via http://localhost:8080/db works, but other operations like insert/update are throwing a MapperException because the system can't find a DB mapper for your Pokemon class.

First, let's highlight the core of the error you're seeing:

Caused by: io.helidon.common.mapper.MapperException: Failed to map class com.oracle.dx4c.taas.poc.common.Pokemon to java.util.Map<java.lang.String, ?>: Failed to find DB mapper.
at io.helidon.dbclient.DbMapperManagerImpl$1.toNamedParameters(DbMapperManagerImpl.java:148)
at io.helidon.dbclient.DbMapperManagerImpl.lambda$toNamedParameters$2(DbMapperManagerImpl.java:62)
at io.helidon.dbclient.DbMapperManagerImpl.executeMapping(DbMapperManagerImpl.java:79)
at io.helidon.dbclient.DbMapperManagerImpl.toNamedParameters(DbMapperManagerImpl.java:61)
at io.helidon.dbclient.common.NamedStatementParameters.namedParam(NamedStatementParameters.java:49)
at io.helidon.dbclient.common.AbstractStatement.namedParam(AbstractStatement.java:125)
at com.oracle.dx4c.taas.poc.common.AbstractPokemonService.lambda$insertPokemon$0(AbstractPokemonService.java:98)
...

This happens because Helidon's DbMapperManager needs an explicit mapper to convert your Pokemon entity into the Map<String, ?> format that MongoDB expects for write operations. Fetch might work because Helidon can do basic reflection-based mapping for reading, but write operations require a dedicated mapper to handle parameter binding properly.

Here's how to fix this step by step:

1. Create a Custom DbMapper for Your Pokemon Class #

You need to implement the io.helidon.dbclient.DbMapper<Pokemon> interface to define how your entity translates to/from MongoDB documents. Here's a sample implementation:

package com.oracle.dx4c.taas.poc.common;

import io.helidon.dbclient.DbMapper;
import io.helidon.dbclient.NamedStatementParameters;
import io.helidon.dbclient.ReadableRow;
import java.util.HashMap;
import java.util.Map;

public class PokemonMapper implements DbMapper<Pokemon> {

    @Override
    public Pokemon read(ReadableRow row) {
        // Map MongoDB document fields to your Pokemon entity (for read operations)
        return new Pokemon(
            row.get("id", Integer.class),
            row.get("name", String.class),
            row.get("type", String.class)
            // Add other fields from your Pokemon class here
        );
    }

    @Override
    public void write(Pokemon pokemon, NamedStatementParameters parameters) {
        // Map Pokemon fields to query parameters (for write operations)
        parameters.add("id", pokemon.getId())
                  .add("name", pokemon.getName())
                  .add("type", pokemon.getType());
        // Add other fields here
    }

    @Override
    public Map<String, ?> toNamedParameters(Pokemon pokemon) {
        // Optional alternative: directly return a map of fields for parameter binding
        Map<String, Object> params = new HashMap<>();
        params.put("id", pokemon.getId());
        params.put("name", pokemon.getName());
        params.put("type", pokemon.getType());
        return params;
    }
}

2. Register the Mapper with Helidon #

You have two options to register your mapper so Helidon can find it:

Option A: Service Loader (Recommended for MP)

Create a file at src/main/resources/META-INF/services/io.helidon.dbclient.DbMapper and add the fully qualified name of your mapper class:

com.oracle.dx4c.taas.poc.common.PokemonMapper

Helidon will automatically discover this mapper using the service loader pattern.

Option B: Programmatic Registration

If you prefer to register it in code, add the mapper when building your DbClient:

DbClient dbClient = DbClient.builder()
    .mapper(Pokemon.class, new PokemonMapper())
    // Add your MongoDB connection configuration here
    .build();

3. Verify Dependencies #

Double-check your pom.xml to ensure you have all necessary Helidon DB MongoDB dependencies:

<dependencies>
    <dependency>
        <groupId>io.helidon.dbclient</groupId>
        <artifactId>helidon-dbclient-mongodb</artifactId>
    </dependency>
    <dependency>
        <groupId>io.helidon.dbclient</groupId>
        <artifactId>helidon-dbclient</artifactId>
    </dependency>
    <!-- Don't forget your Helidon MP dependencies too -->
</dependencies>

4. Check Your Write Operation Code #

Make sure your insertPokemon method is using the mapper correctly. For example, your code should look something like this:

public void insertPokemon(Pokemon pokemon) {
    dbClient.execute(exec -> exec
        .insert("insert-pokemon") // Your named insert statement
        .namedParam(pokemon) // Pass the Pokemon instance - Helidon uses the mapper here
        .thenAccept(count -> System.out.println("Inserted " + count + " Pokemon"))
    );
}

Once you've implemented and registered the mapper, Helidon should be able to convert your Pokemon entity to the required format for write operations, and the exception should be resolved.

内容的提问来源于stack exchange，提问作者Mujibur Rahman