External modules that require registering DataSerializableFixedIDs typically do so as part of their service loading initialization step. However, it seems that under some circumstances it may be necessary to have the DSFIDs be available even before the service is loaded as peers may be sending DSFID values even as a member is just starting up. Thus the DSFID should be made available even before a member is available to receive peer messages.
This change introduces a service loader interface, DSFIDLoader which is called as part of the static initialization block in InternalDataSerializer. This will ensure that all reguired DSFIDs are available almost as soon as the JVM starts.
This work is related to