Adds the ability to complement each other with attributes of annotations and XML tags

Feature Request

Is your feature request related to a problem?

No.

Describe the feature you would like.

In the current version 3.5.9, the configuration of the xml tag and the annotation of the java class cannot complement each other. If the following configuration is used, the configuration in @Option will be invalid.

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE mapper PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN" "http://mybatis.org/dtd/mybatis-3-mapper.dtd" >
<mapper namespace="com.example.mapper.TestMapper">
    <insert id="insertTest">
        insert into test_table (column_a, column_b)
        VALUES (#{object.columnA}, #{object.columnB})
    </insert>
</mapper>

@Mapper
public interface TestMapper{
  @Options(useGeneratedKeys = true, keyColumn = "id", keyProperty = "object.id")
  void insertTest(@Param("object") TestPO object);
}

@Data
@NoArgsConstructor
@AllArgsConstructor
public class TestPO{
    private Long id;
    private String columnA;
    private String columnB;
}

The current Mybatis version can only make the corresponding operations all located in xml tags or all in Java class annotations, like the following.

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE mapper PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN" "http://mybatis.org/dtd/mybatis-3-mapper.dtd" >
<mapper namespace="com.example.mapper.TestMapper">
    <insert id="insertTest" useGeneratedKeys="true" keyProperty="object.id" keyColumn="id">
        insert into test_table (column_a, column_b)
        VALUES (#{object.columnA}, #{object.columnB})
    </insert>
</mapper>

I think this can be handled appropriately, I don’t seem to have flipped through similar discussions.

[awxiaoxian2020]

@linghengqian you know the mapper may be complex and the xml can give more config. And I think we should give all details in one context. As there are no principle to how to simplify the xml or seperate them(xml and annotation) appropriately.

[awxiaoxian2020]

Based on community comments, should I classify this issue as a documentation issue and submit an explicit hint? (I don’t see the relevant instructions, but I’m not sure if this was intentional)

if we add the context for whether valid for the mixture of the specified xml and annotation, there are too many combinations, I don’t know whether we should add contents for this in the doc.

@harawata This is a doc update request. Maybe he want to get the tips when he use the xml and annotation at the same time. What do you think?