Closed adutra closed 3 years ago
Currently we require from users to write some boilerplate code to register Dao beans:
public class FruitDaoProducer { private final FruitDao fruitDao; @Inject public FruitDaoProducer(QuarkusCqlSession session) { FruitMapper mapper = new FruitMapperBuilder(session).build(); fruitDao = mapper.fruitDao(); } @Produces @ApplicationScoped FruitDao produceFruitDao() { return fruitDao; } }
It would be nice if we could detect all interfaces annotated with @Mapper and @Dao and automatically expose all the Dao implementations.
@Mapper
@Dao
This may be related to #112.
┆Issue is synchronized with this Jira Task by Unito
This may prevent Daos from being parameterized by keyspace or table.
Currently we require from users to write some boilerplate code to register Dao beans:
It would be nice if we could detect all interfaces annotated with
@Mapper
and@Dao
and automatically expose all the Dao implementations.This may be related to #112.
┆Issue is synchronized with this Jira Task by Unito