java/proto/src/main/java/com/pravala/protocol/Serializable.java
public void serializeData ( OutputStream writeTo ) throws IOException, CodecException
    {
        // If we 'define' and alias, we are safe to do this first and call 'serialize'
        // in our ancestor later (which could, potentially, define the storage type itself
        // overwriting our value). However, the protocol compiler should not allow
        // storage (aliased) types to be defined (and vice versa).
        setupDefines();

        validate();

        serializeAllFields ( writeTo );
    }
/**
     * Serializes content of the message
     *
     * It just appends content to the buffer.
     * First the serializeData() from inherited object is called.
     * Next, all present, local fields are serialized -
     * either by serializing them directly, or by calling their serializeData()
     * This function does not encode base message's length.
     * To encode a complete message you need to call serialize()
     * from the base message class (and that is the only function that should
     * be used in most cases - usually there is no need to call serializeData() directly)
     * @param writeTo Where to serialize data
     * @throws IOException, CodecException
     */
Serializes content of the message
It just appends content to the buffer.
First the serializeData() from inherited object is called.
Next, all present, local fields are serialized
either by serializing them directly, or by calling their serializeData()
This function does not encode base message's length.
To encode a complete message you need to call serialize()
from the base message class (and that is the only function that should
be used in most cases - usually there is no need to call serializeData() directly)
@param writeTo Where to serialize data
@throws IOException, CodecException
Serializes content of the message It just appends content to the buffer . First the serializeData () from inherited object is called . Next all present local fields are serialized either by serializing them directly or by calling their serializeData () This function does not encode base message ' s length . To encode a complete message you need to call serialize () from the base message class ( and that is the only function that should be used in most cases - usually there is no need to call serializeData () directly ) @param writeTo Where to serialize data @throws IOException CodecException
public void serializeData ( OutputStream writeTo ) throws IOException, CodecException
    {
        setupDefines();
        validate();
        serializeAllFields ( writeTo );
    }
public void serializeData ( OutputStream writeTo ) throws IOException , CodecException { setupDefines ( ) ; validate ( ) ; serializeAllFields ( writeTo ) ; }
Serializes content of the message
 It just appends content to the buffer.
Serializes content of the message It just appends content to the buffer .
// If we 'define' and alias, we are safe to do this first and call 'serialize' // in our ancestor later (which could, potentially, define the storage type itself // overwriting our value). However, the protocol compiler should not allow // storage (aliased) types to be defined (and vice versa).