Details
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
Attachments
Issue Links
- relates to
-
IGNITE-10075 .NET: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET
- Resolved
- links to