Allow generating any namespace in MyBatisDataAccessStrategy [DATAJDBC-178]

[spring-projects-issues]

Kazuki Shimizu opened DATAJDBC-178 and commented

In current implementation, namespace rule("FQCN of domain type" + "Mapper") cannot customize.
I will propose to add a naming strategy for allowing to customize namespace rule.

e.g.)

public interface MyBatisNamingStrategy {
	default String getNamespace(Class<?> domainType) {
		return domainType.getName() + "Mapper";
	}
}

---

Referenced from: pull request #44, and commits 45a6d34, 01a4bbd, c7958f8

[spring-projects-issues]

Jens Schauder commented

Could you elaborate a little why you think this is important? Why would one want to customize the naming strategy?

[spring-projects-issues]

Kazuki Shimizu commented

Sorry for late reply.
In my experience, there are many cases that domain objects, repositories and mappers is separated to another package.

e.g.)

+ com
    + example
         + domain
              - User.class
         + repository
              - UserRepository.class
         + mapper
              - UserMapper.class
              - UserMapper.xml (optional)

Hence; I want to allow customize a namespace of Spring Data JDBC.

WDYT?

[spring-projects-issues]

Jens Schauder commented

I kind of forgot about the mapper class and only thought about the XML. With that in mind, it probably does make sense to have some flexibility