[IGNITE-23368] Refactor processing of LazyServiceConfiguration

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.14
• Labels: ise
• Assignee: Unassigned
• Reporter: Nikita Amelchev
• Created: 04/Oct/24 14:08
• Updated: 04/Oct/24 21:25

Description

• We should get rid of `instance of LazyServiceConfiguration` usages. It is always the extended configuration with normal deployment, with the public API. No need to check/cast.
• The ServiceConfiguration class should not participate in serialization. The extended configuration should be `Externalizable` for example. `LazyServiceConfiguration` should not have the duplicates of the base `ServiceConfiguration`s `IgnitePredicate<ClusterNode> nodeFilter`, `ServiceCallInterceptor[] interceptors` and probably `Service svc`.
• Revisit #toString method. It might give more info like `serviceName`, `nodeFilterClass`, `totalCnt`, `perNodeCnt`, etc.
• Is the name "lazy" appropriate for this class? Maybe like `BinaryServiceConfiguration`, or `SerializationServiceConfiguration`, or `ExtendedServiceConfiguration`.

Issue Links

• is related to: IGNITE-23202 Services: node crashes when node filter class was not found in class path