[IGNITE-14169] .NET: Support standard Java naming conventions in the name mapper

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.1
• Fix Version/s: 2.10
• Component/s: platforms
• Labels: .NET
• Release Note: .NET: Added NamespacePrefix and NamespaceToLower to BinaryBasicNameMapper
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Nikolay Izhikov
• Reporter: Nikolay Izhikov
• Created: 12/Feb/21 09:10
• Updated: 25/Feb/21 11:39
• Resolved: 16/Feb/21 11:49

Description

Currently, BasicBinaryNameMapper[isSimpleName=false] assumes that type names equals both in Java and .Net.

Java type - ru.company.Model
.Net type - ru.company.Model

However, .net naming conventions [1] differs from java [2]
So, if a user follows both conventions then names will be

Java type - ru.company.Model
.Net type - Ru.Company.Model

We should support standard naming conventions for both platforms in BasicBinaryNameMapper[isSimpleName=false].

[1] https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/names-of-namespaces
[2] https://www.oracle.com/java/technologies/javase/codeconventions-namingconventions.html

Issue Links

• relates to: IGNITE-10075 .NET: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET
• links to: GitHub Pull Request #8795