public void registerAll() {

        // See if we will have problems because our registry is locked        
        if( Serializer.isReadOnly() ) {
            // Check to see if maybe we are executing this from the
            // same JVM that sent the message, ie: client and server are running on
            // the same JVM
            // There could be more advanced checks than this but for now we'll
            // assume that if the registry was compiled here then it means
            // we are also the server process.  Note that this wouldn't hold true
            // under complicated examples where there are clients of one server
            // that also run their own servers, but realistically they would have
            // to disable the ServerSerializerRegistrationsServer anyway.
            if( compiled != null ) {
                log.log(Level.INFO, "Skipping registration as registry is locked, presumably by a local server process.");
                return;
            }
        }
        
        log.log(Level.FINE, "Registering {0} classes...", registrations.length);
        for( Registration reg : registrations ) {
            log.log(Level.INFO, "Registering:{0}", reg);
            reg.register();
        }
        log.log(Level.FINE, "Done registering serializable classes.");
    }
Holds a compiled set of message registration information that
 can be sent over the wire.  The received message can then be
 used to register all of the classes using the same IDs and 
 same ordering, etcetera.  The intent is that the server compiles
 this message once it is sure that all serializable classes have
 been registered.  It can then send this to each new client, and
 they can use it to register all of the classes without requiring
 exactly reproducing the same calls that the server did to register
 messages.

 <p>Normally, JME recommends that apps have a common utility method
 that they call on both client and server.  However, this makes 
 pluggable services nearly impossible as some central class has to
 know about all registered serializers.  This message implementation
 gets around by only requiring registration on the server.</p>

 @author    Paul Speed
jme3-networking/src/main/java/com/jme3/network/message/SerializerRegistrationsMessage.java