Spring Cloud Function函数式Bean注册下如何自动生成BookRepository实例

Great question! When moving to functional bean registration in Spring Cloud Function, you're right that Spring Data's dynamic repository proxies won't be created automatically since component scanning is disabled. Here's how you can keep those auto-generated CRUD methods without writing all the implementations yourself:

Method 1: Use @EnableDynamoDBRepositories (Simplest Approach) #

Even if you've turned off general component scanning, Spring Data DynamoDB's @EnableDynamoDBRepositories annotation works independently to scan and create repository proxies. You just need to register the configuration class holding this annotation in your functional context.

First, create a configuration class for DynamoDB:

@Configuration
@EnableDynamoDBRepositories(basePackageClasses = BookRepository.class)
public class DynamoDBConfig {
    // Register core DynamoDB beans first
    @Bean
    public AmazonDynamoDB amazonDynamoDB() {
        // Configure your client with region, credentials, etc.
        return AmazonDynamoDBClientBuilder.standard()
                .withRegion(Regions.US_EAST_1)
                .build();
    }

    @Bean
    public DynamoDBMapper dynamoDBMapper(AmazonDynamoDB amazonDynamoDB) {
        return new DynamoDBMapper(amazonDynamoDB);
    }

    @Bean
    public DynamoDBOperations dynamoDBOperations(DynamoDBMapper dynamoDBMapper) {
        return new DynamoDBTemplate(dynamoDBMapper);
    }
}

Then register this configuration class in your functional context:

GenericApplicationContext context = new GenericApplicationContext();
context.registerBean(DynamoDBConfig.class);
context.refresh();

Spring Data will automatically generate the proxy for BookRepository with all CRUD methods and your custom findAllByAuthor method implemented.

Method 2: Manually Create Repository Proxy via DynamoDBRepositoryFactory #

If you want a fully functional, annotation-free approach, you can use Spring Data DynamoDB's repository factory to create the proxy instance manually and register it as a bean.

GenericApplicationContext context = new GenericApplicationContext();

// First register core DynamoDB beans
context.registerBean(AmazonDynamoDB.class, () -> 
        AmazonDynamoDBClientBuilder.standard()
                .withRegion(Regions.US_EAST_1)
                .build());

context.registerBean(DynamoDBMapper.class, (ctx) -> 
        new DynamoDBMapper(ctx.getBean(AmazonDynamoDB.class)));

context.registerBean(DynamoDBOperations.class, (ctx) -> 
        new DynamoDBTemplate(ctx.getBean(DynamoDBMapper.class)));

// Now create and register the BookRepository proxy
context.registerBean(BookRepository.class, (ctx) -> {
    DynamoDBRepositoryFactory factory = new DynamoDBRepositoryFactory(ctx.getBean(DynamoDBOperations.class));
    return factory.getRepository(BookRepository.class);
});

context.refresh();

This approach directly uses Spring Data's factory to generate the dynamic proxy, so you get all the auto-implemented CRUD methods without writing any boilerplate.

Key Notes: #

• Never try to instantiate the repository interface directly (like new BookRepository() { ... })—Spring Data repositories are dynamic proxies generated at runtime, so you need to use the factory or annotation-driven approach.
• Ensure your core DynamoDB beans (AmazonDynamoDB, DynamoDBMapper, DynamoDBOperations) are properly configured and registered before the repository, as the factory depends on them.

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