Bug #35786 Incorrect alert for innodb_support_xa =1 when replication/binlog enabled

Description:
Manual clearly states (http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html#option_mysqld_innodb_support...):

--->>
If you are using replication and/or the binary log then you should set this variable to ON or 1 to ensure that the binary log does not get out of sync compared to the table data. 
<<---

But we get such alert on Master server:

--->>
Advisor: Administration - XA Distributed Transaction Support Enabled For InnoDB

Problem Description
XA Distributed Transaction support is turned on by default. If you are not using this feature, note that it adds an extra fsync for each transaction and may adversely affect performance.

Advice
Turn off XA distributed transaction support if you do not need it: Add innodb_support_xa=0 to your my.cnf/my.ini file and restart the server.

Recommended Action
SET GLOBAL innodb_support_xa = 0;
<<---

So customers not sure when they should consider that alert valuable.
Maybe that is DOC bug, but now it clearly states to set innodb_support_xa = 1 when using Replication.

How to repeat:
Advisers on Master server. 

Suggested fix:
Do not alarm that warning in case when binlog enabled. (or clearly state possible out-of-sync results in Advise/Recommended Action sections).

Thank you for a problem report.

Added "&& (%log_bin% = "OFF")" to the expression.

Committed revision 9125.

Rule "XA Distributed Transaction Support Enabled For InnoDB" now does not send the warning when the binary log is on.

Verified fixed in advisor build 1.3.0.9137.

Set to "verified" with a "target" of 2.0 as requested.

Also added an entry to the 1.3 changelog:

The rule “XA Distributed Transaction Support Enabled For InnoDB” incorrectly sent a warning when the binary log was on.

This was fixed in the 2.0 codeline at the same time it was fixed in 1.3, so please re-test with the latest 2.0 stuff.

Verified fixed in advisor build 2.0.0.7019.

Updated 2.0 changelog.