[
https://issues.apache.org/jira/browse/IGNITE-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15121023#comment-15121023
]
Pavel Tupitsyn commented on IGNITE-1906:
----------------------------------------
1) I agree. We can remove both of them. Yes, XML config will get a bit more
verbose, but it will be easier to understand.
2) Why?
3) Unfortunately, only compile-time constants are allowed in attribute
declarations. TimeSpans are not compile-time constants. Yes, this leads to
duplication in Default attributes, but we need them for runtime introspection
(for example, to ignore default property values during XML config
serialization). This is inconvenient, but only for us, not for users.
4) I think we should. TimeSpan is a standard way of representing timeouts and
such (see WCF or ASP.NET configs, all timeouts are this way). "h", "h:m",
"h:m:s" and other string representations are allowed. Using long there will
certainly be confusing.
> .Net: Ignite configuration without Spring
> -----------------------------------------
>
> Key: IGNITE-1906
> URL: https://issues.apache.org/jira/browse/IGNITE-1906
> Project: Ignite
> Issue Type: Task
> Components: interop
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Fix For: 1.6
>
>
> * Spring is alien for .NET developers
> * In-code configuration is often preferrable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
