Feauture/convert xml to java conf

[Akvel]

Description

This PR convert Spring XML based configurations to Java-Configurations.

Converted beans that can be easily converted by scripts. I think this PR could be first step to Java-based configuration in all project.

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

How Has This Been Tested?

mvn test

[weizhouapache]

@blueorangutan package

[blueorangutan]

@weizhouapache a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

[DaanHoogland]

quite a great effort. I wouldn't mind this excpet that the removed licenses are probably not acceptable in apache by-laws. Also can you justify this chance with a bit more text, please?

[DaanHoogland]

removing the license is not acceptable in apache foundation policy

[Akvel]

fixed, also added to all new java classes

[blueorangutan]

Packaging result: ✖️ el7 ✖️ el8 ✖️ debian ✖️ suse15. SL-JID 1437

[ravening]

This backup file can be excluded

[Akvel]

fixed

[ravening]

this backup file can be excluded

[Akvel]

fixed

[ravening]

same here

[Akvel]

fixed

[DaanHoogland]

@Akvel thanks for joining in, can you add some context for us to understand your morives behind this PR, please? Especially because it is not eliminating the XML completely, what are we gaining going ahead with this?

[Akvel]

thanks for joining in, can you add some context for us to understand your morives behind this PR, please? Especially because it is not eliminating the XML completely, what are we gaining going ahead with this?

@DaanHoogland I am converted beans that can be easily converted by scripts. I think this PR could be first step to Java-based configuration in all project.

[DaanHoogland]

thanks @Akvel can you add that explanation to the description of the PR, please?
Also, such a decision should be discussed in a wider audience, so cc @weizhouapache @RodrigoDLopez @rhtyd @GabrielBrascher @sureshanaparti @ravening @GutoVeronezi . I really shouldn't cc so many people at once but the subject merits it.

[Akvel]

thanks @Akvel can you add that explanation to the description of the PR, please? Also, such a decision should be discussed in a wider audience, so cc @weizhouapache @RodrigoDLopez @rhtyd @GabrielBrascher @sureshanaparti @ravening @GutoVeronezi . I really shouldn't cc so many people at once but the subject merits it.

done

[RodrigoDLopez]

Thanks for the PR @Akvel. I liked the proposal.
But like everyone else who will be participating in this here, I have my fears about community approval.
I believe that starting a vote on the email list is the best way (with arguments that reinforce the need and, if necessary, a contextualization of the problem). As soon as the community approves, we return to the PR and discuss the possible points raised in the vote.

[ravening]

@DaanHoogland will test it out soon

[github-actions]

Hi @${author}, your pull request has merge conflicts. Can you fix the conflicts and sync your branch with the base branch?

[DaanHoogland]

@Akvel @ravening are you guys still on this?

[DaanHoogland]

@Akvel et al, closing this one as it has conflicts and is old. please update and reopen if you think it is still relevant.