Pavel,
The configuration framework is designed to support dynamic configuration
changes - I doubt this is needed for the client side. I think we should
start with simple POJOs or builders.
-Val
On Sat, Aug 21, 2021 at 7:03 AM Ivan Daschinsky wrote:
> As for me, it is very strange purpose and
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
As for me, it is very strange purpose and not very practical. I can hardly
imagine why someone will use it. For example, if I use micronaut or spring,
this dependency will make me angry
сб, 21 авг. 2021 г., 16:13 Pavel Tupitsyn :
> Ivan, the purpose is to be able to configure thin client with
Ivan, the purpose is to be able to configure thin client with HOCON.
On Sat, Aug 21, 2021 at 3:37 PM Ivan Daschinsky wrote:
> Hi. As for me, it is quite strange to make thin client dependent on third
> party libraries like hocon parser and so on. What's the purpose of this?
>
> сб, 21 авг. 2021
Hi. As for me, it is quite strange to make thin client dependent on third
party libraries like hocon parser and so on. What's the purpose of this?
сб, 21 авг. 2021 г., 13:32 Pavel Tupitsyn :
> Igniters,
>
> I'd like to discuss Java thin client configuration API in Ignite 3.0.
>
> On one hand, it
Igniters,
I'd like to discuss Java thin client configuration API in Ignite 3.0.
On one hand, it would be nice to use codegen approach from
ignite-configuration module,
and have consistent config APIs across servers and thin clients.
On the other hand, that API may seem a bit confusing, because
