I think this bug may be outdated. It is very old and it appears the chapters have been updated. It is in the same section as other datasource configuration topics. 

  Section: Transaction Subsystem Configuration
    Transactions Configuration Overview [4374]
    Section: Transactional Datasource Configuration
      Configure Your Datasource to Use JTA Transactions [4295]
      Configure an XA Datasource [4303]
      Log in to the Management Console [3569]
      Create a Non-XA Datasource with the Management Interfaces [4805]
      Datasource Parameters [2772]

Can you please verify that it's correct now?

This topic appears in both the Development Guide and in the Administration and Configuration Guide. The above is the Development Guide.

The following is the Admin Guide:

  Section: Datasource Configuration
    Datasource Parameters [2772]
    Datasource Connection URLs [6184]
    Datasource Extensions [4643]
    View Datasource Statistics [13918]
    Datasource Statistics [13779]
  Section: Example Datasources
    Example PostgreSQL Datasource [5688]
    Example PostgreSQL XA Datasource [5689]
    Example MySQL Datasource [5690]
    Example MySQL XA Datasource [5691]
    Example Oracle Datasource [5696]
    Example Oracle XA Datasource [5697]
    Example Microsoft SQLServer Datasource [5698]
    Example Microsoft SQLServer XA Datasource [5699]
    Example IBM DB2 Datasource [5700]
    Example IBM DB2 XA Datasource [5701]
    Example Sybase Datasource [8847]
    Example Sybase XA Datasource [8848]

Hi,

yeap, agree, it's correct now.

Thank you
Ondra

Moving this directly to ON_QA.

This can be verified at the following links:

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Administration_and_Configuration_Guide/index.html#Datasource_Parameters1

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Datasource_Parameters1

This was a bit outdated issue and it was fixed already for 6.2.
Thanks