[BUG] @Reference#parameters() does not work

[mercyblitz]

• I have searched the issues of this repository and believe that this is not a duplicate.
• I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

• Dubbo version: 2.6.3
• Operating System version: all
• Java version: all

Step to reproduce this issue

1. To setting @Reference#parameters()

Expected Result

ReferenceBean contains parameters Map

Actual Result

ReferenceBean does not contain parameters Map

[diecui1202]

@mercyblitz could u pls. send a PR?

[cvictory]

I write a demo to check this issue, but I found ReferenceBean has this parameter.

modify dubbo configuration file :

    <dubbo:annotation/>
    <context:component-scan base-package="com.alibaba.dubbo.demo.consumer">
        <context:include-filter type="annotation" expression="com.alibaba.dubbo.config.annotation.Reference"/>
    </context:component-scan>

write service:

@Service
public class ConsumerService {

    @Reference(parameters = {"k1", "v1"})
    private DemoService demoService;

    public void testReference() {
        System.out.println(demoService.sayHello("www.world"));
    }
}

And debug the referenceConfig, I found the parameter contain this key as follow:

I write a demo to check this issue, but I found ReferenceBean has this parameter.

modify dubbo configuration file :

    <dubbo:annotation/>
    <context:component-scan base-package="com.alibaba.dubbo.demo.consumer">
        <context:include-filter type="annotation" expression="com.alibaba.dubbo.config.annotation.Reference"/>
    </context:component-scan>

write service:

@Service
public class ConsumerService {

    @Reference(parameters = {"k1", "v1"})
    private DemoService demoService;

    public void testReference() {
        System.out.println(demoService.sayHello("www.world"));
    }
}

And debug the referenceConfig, I found the parameter contain this key as follow:

[cvictory]

@mercyblitz please check this issue again.

&READY-TO-CLOSE&

[cvictory]

@mercyblitz I saw you have a commit to this issue. Maybe you should commit a dependent pr and related to this issue.