Camel-syslog dataformat broken with netty transport

in Rfc3164SyslogDataFormat, the remoteAddress of the SyslogMessage is set from the Mina or Netty headers. There's a copy/paste error for Netty: it correctly checks for the existence of the CamelNettyRemoteAddress header, but then attempts to set the remoteAddress from a CamelMinaRemoteAddress header.

(there's no camel-syslog component in JIRA)