How does Mule handle XML configuration that doesn't comply with its XML schema?
I've been assigned to work on a legacy system using Mule 2 and I've found some quirks in some of the old configuration. The developers who originally wrote the documentation has changed jobs so nobody has dared to change anything since. 

    <service name="taskCompleted">
            <inbound>
                <jms:inbound-endpoint topic="namespace.transporttask.completed">
                    <jms:jmsmessage-to-object-transformer />

                    <!-- This section does not comply with Mule's XML schema 
                         (Element message-properties-transformer is not allowed here) -->
                    <message-properties-transformer>
                        <add-message-property key="MULE_ENCODING" value="windows-1252" />
                    </message-properties-transformer>
                </jms:inbound-endpoint>
            </inbound>
            <bridge-component />
            <outbound>
                ...
            </outbound>
        </service>

This is just one of the examples I've found and my assumption is that Mule just ignores configuration like this and that it's safe to remove it as it probably doesn't do anything. Is this assumption correct? 
How does Mule handle XML configuration that doesn't comply with its XML schema?
===

I've been assigned to work on a legacy system using Mule 2 and I've found some quirks in some of the old configuration. The developers who originally wrote the documentation has changed jobs so nobody has dared to change anything since. 

    <service name="taskCompleted">
            <inbound>
                <jms:inbound-endpoint topic="namespace.transporttask.completed">
                    <jms:jmsmessage-to-object-transformer />

                    <!-- This section does not comply with Mule's XML schema 
                         (Element message-properties-transformer is not allowed here) -->
                    <message-properties-transformer>
                        <add-message-property key="MULE_ENCODING" value="windows-1252" />
                    </message-properties-transformer>
                </jms:inbound-endpoint>
            </inbound>
            <bridge-component />
            <outbound>
                ...
            </outbound>
        </service>

This is just one of the examples I've found and my assumption is that Mule just ignores configuration like this and that it's safe to remove it as it probably doesn't do anything. Is this assumption correct? 