Good catch! 

However, this fix lead the following question: why this test was not failing up to now? Context Broker is not currently taking into account Content-Type to call the corresponding parsing (either JSON or XML)?